Compliance and Auditing Tools 459 plenty of resources (such as disk space) for SQL Server to run properly. Because the data and structure of Microsoft Dynamics CRM are completely contained within the database instances underlying the application, Microsoft Dynamics CRM can be restored from any point both at which the organization database and the configura- tion databases are backed up. So whether you have nightly, weekly, or monthly backups of your database, make sure you capture both the organization database (or databases, if you are using a multitenant deployment) and the configuration database. After regular backups, the next most pressing concern to keep SQL Server in peak running order is to defragment the database so that the indexes will do their job and speed up queries instead of slow them down. Indexes on highly used tables-- those with the most insertions, updates, and deletions--can become fragmented across a hard drive and slow down queries on those tables. It is important to regu- larly check and defragment these indexes, if appropriate. Finally, another thing that can cause trouble for a SQL Server is not having enough resources. Whether it is CPU resources, memory, or disk space available, SQL Server generally requires a good deal of it to run at peak performance. That is why it is important to know when one of these resources is running low and take the appropriate action to fix