Data management is a key component to your Introspect reporting performance. To that end, we have found that in any sized Citrix XenApp farm, the size of the Resource Manager (RM) summary database can become large quite fast and impact reporting performance. This is mainly due to the unnecessary capture of process data that is not relevant in any historical analysis. We want to make sure all of our customers have the best experience, regardless of the size of historical data they collect. In order to ensure top performance of Introspect with Analysis Services 2005, here are our recommended data management best practices.

1. Citrix Resource Manager captures a large amount of process related information about processes being run under a user session. Some of this information is useful for historical analysis and some offer little value. We have created a SQL query template that can be easily modified to delete the data collected from processes you deem unnecessary. Just follow the steps included in the attached document to update the query and run against your summary database. We strongly suggest taking a backup of the database before deleting any data. NOTE: You must register as a customer to download this document. If you haven't, you can do so here .

2. After following Step 1 to clean up your summary database, to avoid the RM summary database from growing unnecessarily large in the future a good approach is to only store relevant, useful information for historical analysis. To ensure that only relevant information is stored in the summary database, use the Citrix Management Console to ignore processes from being captured. Click on this link to determine how to ignore process in Citrix XenApp 4.x.

Besides improving reporting performance, another reason to manage the size of your summary database if that the size of this data could result in the failure of the XTS Analytics Database processing if the processing task reaches 2GB of memory. If you encounter this problem, for a 32 bit OS only, change application memory versus operating system ratio from 2GB : 2GB to 3 GB: 1GB. This in effect increases memory available to applications from 2 GB to 3 GB. Following the prior steps to manage the size of your summary database will reduce the likelihood of this processing problem.

In the rare occurrence that you still are encountering memory related processing issues with Analysis Services 2005, you may solve the problem by installing Analysis Services 2005 only on a 64 bit OS. Keep in mind, the Introspect console can only be installed on 32 bit OS, however Analysis Services can be separate installed on 64 bit OS.

If you want to discuss which processes to delete or have other questions, please contact support@xtsinc.com.