In a XenApp environment, all farm wide configuration information is stored in the IMA database. The IMA service primarily performs queries on the IMA database and in order to speed up the query performance, many table indexes are created on the IMA database's tables.
Occasionally the IMA service needs to make changes to the IMA database - for example, during the application publishing process, during the policy editing process, etc. Over time, these data update operations will cause the indexes to become fragmented and less organized. There will be more page splits, a greater number of pages with less data on them, and consequently there will be more I/O required to satisfy each query.
When the data and index become fragmented the IMA service query performance will be degraded. This impacts the performance of events such as IMA service startup time, Access Management Console discovery time and Local Host Cache update time. In order to improve the performance of IMA service queries, some database maintenance operations should be performed on the IMA database.
As an example of the recommended database maintenance operations, the following provides the actions that can be performed on SQL Server 2000. To accomplish similar procedures on Oracle, IBM DB2 and SQL Server 2005, consult the accompanying documentation for your database.
- Start the Database Maintenance wizard from Enterprise Manager, click Next
- Select your IMA database, click Next.
- Select "Reorganize the data and index pages," click Next
- On the "Specify the Database Backup Plan" window, ensure the check box "Back up the database as part of the maintenance plan" is cleared. Click Next.
- Accept the default options for the following wizard windows. Name this maintenance plan and click Finish.
 | Note
Index reorganization can also be included as part of a regular database maintenance plan that includes database backup. |
