This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 13874 (Plato7x)
The memory used by the Analysis Services server process, Msmdsrv.exe, does not decrease as expected after it runs an incremental update on a cube or a partition that contains a Distinct Count measure.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack
The English version of this fix 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 -------------------------------------------------------------- 12-Feb-2003 02:49 8.0.767.0 1,024,576 bytes Msmdgd80.dll 27-Jan-2003 07:47 18.104.22.1681 9,638,464 bytes Msmdsgn80.dll 14-Feb-2003 22:32 8.0.768.0 1,827,396 bytes Msmdsrv.exe 12-Feb-2003 02:49 8.0.767.0 2,069,072 bytes Msolap80.dll
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.
SQL Server 2000 Analysis Services 64-bit
For additional information about a hotfix build designed to be applied on a server that is running SQL Server 2000 Analysis Services 64-bit, or to find out 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:
822017 FIX: Hotfix Information for Build 8.0.810.0 of SQL Server 2000 Analysis Services 64-bit
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.
Generally, you see an increase in memory when performing a process operation in Analysis Services. Typically, the size of the memory increase is directly related to the type of object that is being processed. When processing a dimension, the memory increase is usually approximately the size of the dimension plus the size of the Read-ahead and the process buffer settings for Analysis Services. After the processing completes, the memory should return to the pre-processing levels, unless this is the first time the dimension was processed. The first time the dimension is processed, the memory usage will increase by the size of the dimension because it is now loaded in the server memory space. When Analysis Services processes a cube, the memory usage on the server will increase by the size of the Read-ahead and the process buffers during processing. The memory usage should return to pre-processing levels after the processing completes.
When this problem occurs, the memory usage of the Analysis Services server process does not decrease to the pre-processing levels after running an incremental update on a partition that contains a Distinct Count measure or after merging two partitions of a cube that contain a Distinct Count aggregation. The memory usage increase depends on the size of the partitions that are being processed or merged, and the size of the process buffer.