FIX: When you run an MDX query for the second time, the query does not run faster than the first time that you ran the query in SQL Server 2005 Analysis Services

In Microsoft SQL Server 2005 Analysis Services, you run a multidimensional expressions (MDX) query that takes a long time to execute. When you run the MDX query for the second time, you expect that the query will run faster than the first time because the cache should be used. However, the query runs as slowly as the first time that you ran the query.

This issue occurs because SQL Server 2005 Analysis Services incorrectly cleans the cache even though the server is not under memory pressure.

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

You can see this issue by monitoring the following two counters in System Monitor:

• The Private Bytes counter of the Process object
• The Cleaner Memory KB counter of the MSAS 2005:Memory object

Note For a named instance of SQL Server 2005 Analysis Services, the object name is as follows:Notice that the Cleaner Memory KB counter increases faster than the Private Bytes counter. This occurs because SQL Server 2005 Analysis Services cleans the cache, even though the server is not under memory pressure.

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: