FIX: A memory leak occurs when you process a cube in Analysis Services

View products that this article applies to.

Bug #: 14182 (Plato7x)

SYMPTOMS

When you perform an incremental update or a full process of a cube in Microsoft SQL Server 2000 Analysis Services, the memory consumption of the Msmdsrv.exe process continues to increase. Additionally, some memory is not released as free memory after the process is completed.

Back to the top

RESOLUTION

Service pack information

To 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:

290211 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

The English version of this hotfix has the file attributes (or later file attributes) 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
   --------------------------------------------------------------
   03-Nov-2003  17:08  8.0.874.0         217,668  Msmdcb80.dll     
   28-Oct-2003  02:58  8.0.0.872       4,059,716  Msmddo80.dll     
   03-Nov-2003  17:08  8.0.874.0       1,032,768  Msmdgd80.dll     
   28-Oct-2003  02:58  8.0.823.0         172,608  Msmdpump.dll     
   28-Oct-2003  02:58  8.0.0.864       9,638,468  Msmdsgn80.dll    
   03-Nov-2003  17:08  8.0.874.0       1,835,588  Msmdsrv.exe      
   03-Nov-2003  17:08  8.0.874.0       2,077,264  Msolap80.dll     
   10-May-2003  08:05  8.0.820.0         213,069  Msolap80.rll

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Back to the top

STATUS

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.

Back to the top