FIX: Multiple problems occur when you run a SQL Server 2005 Analysis Services MDX query that uses the DrillDownMember function (913859)


The information in this article applies to:

  • Microsoft SQL Server 2005 Analysis Services
Bug number: 237 (SQL Hotfix)

Microsoft distributes Microsoft SQL Server 2005 fixes 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 200x fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing the hotfix package
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you repeatedly run a Microsoft SQL Server 2005 Analysis Services Multidimensional Expressions (MDX) query, you experience the following symptoms:
  • Every time that you run the query, it takes longer to finish. For example, the first time that you run the query, it might take 15 seconds to finish. When you run the same query again, it might take 36 seconds or more to finish.
  • If you monitor memory consumption on the server from which you run the query, you notice that private bytes usage and virtual bytes usage quickly increase.
  • If you run the query a particular number of times, you receive the following error message:
    Memory error: Allocation failure : Not enough storage is available to process this command.
Note This problem occurs when you use the MDX query together with the DrillDownMember() function.

CAUSE

This problem occurs because of a memory leak in the DrillDownMember() function.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

There are no prerequisites for this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, this hotfix stops and then restarts the Analysis Services service. If you configured the server for HTTP access, you must stop Microsoft Internet Information Services (IIS), and then restart IIS after the installation is finished. If you installed Analysis Services as a named instance, you must stop the SQL Server Browser service. You must do this because the Msmdredir.dll component of the SQL Server Browser service is updated during the installation of this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
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 item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Msmdlocal.dll9.0.1520.015,589,08027-Jan-200612:54x86
Msmdpump.dll9.0.1520.03,913,94427-Jan-200612:54x86
Msmdredir.dll9.0.1520.03,927,25627-Jan-200612:54x86
Msmdsrv.exe9.0.1520.014,567,12827-Jan-200612:54x86
Msmgdsrv.dll9.0.1520.05,935,83227-Jan-200612:54x86
Msolap90.dll9.0.1520.04,204,76027-Jan-200612:54x86

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 SQL Server 2005 Service Pack 1.

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbfix kbBug kbsql2005presp1fix kbHotfixServer kbQFE kbpubtypekc KB913859 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.