Article ID: 841178 - View products that this article applies to.
Bug #: 14332 (Plato7x)
Microsoft SQL Server 2000 fixes are distributed as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
If you run a Multidimensional Expressions (MDX) query for a connection to a SQL Server 2000 Analysis Services server computer, and the Cache Policy connection property's value is set to 7 when the connection is established, the Analysis Services service may shut down.
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ---------------------------------------------------------------- 05-May-2004 19:56 8.0.940.0 221,760 Msmdcb80.dll 05-May-2004 19:56 188.8.131.520 4,063,808 Msmddo80.dll 05-May-2004 19:45 8.0.940.0 1,032,768 Msmdgd80.dll 05-May-2004 19:34 8.0.940.0 172,608 Msmdpump.dll 05-May-2004 20:11 184.108.40.2060 9,638,468 Msmdsgn80.dll 05-May-2004 19:40 8.0.940.0 1,835,588 Msmdsrv.exe 05-May-2004 20:15 8.0.940.0 2,081,360 Msolap80.dll 05-May-2004 18:04 8.0.940.0 213,068 Msolap80.rll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
SQL Server 2000 Analysis Services 64-bitFor additional information about a hotfix build that is designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to see if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/831653/ )Availability of Analysis Services 2000 64-bit hotfix build
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
You can use the Cache Policy connection property in Analysis Services to control the algorithm that is used by the client to determine which data members to request to resolve an MDX query. Typically, the default value provides optimal performance for standard queries. However, the database administrator may sometimes decide that a different Cache Policy value should be used for selected queries.
This hotfix includes a fix that addressed an issue that causes the corruption of dimensions when a Lazy Aggregation processing thread is executed after it processes dimensions that are used in virtual dimensions. Because of that fix, if you incrementally process a virtual dimension, a lazy aggregation processing thread executes. While the lazy aggregation thread executes, the aggregations for that dimension are deleted from each partition.
The lazy aggregation thread executes as a low priority background thread and rebuilds the aggregations for the dimension in each partition. While the lazy aggregation thread executes to rebuild the aggregations, MDX query execution may be significantly slower. The degradation in query performance occurs because of the lack of aggregations. The lack of aggregators causes the server to read values from the leaf level of each partition.
After the lazy aggregation thread finishes rebuilding the aggregations for each partition, you no longer see the degradation in query performance. The query performance degradation during lazy aggregation may be unacceptable in certain situations, such as in high-demand cubes in enterprise applications. If applying this hotfix causes unacceptable query performance degradation, we recommend that you consider the following alternatives during lazy aggregation:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates