FIX: An MDX query that uses the unique name property returns incorrect results when you use a client tool to run the query in SQL Server 2005 Analysis Services (914597)


The information in this article applies to:

  • Microsoft SQL Server 2005 Analysis Services
Bug #346 (SQL Hotfix)
Bug #408069 (SQLBUDT)
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 2005 fix release.

SUMMARY

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

SYMPTOMS

Consider the following scenario:
  • You use a client tool to run an MDX query in SQL Server 2005.
  • The client tool specifies a value of 2 for the MDX Compatibility property in the connection string.
  • The query returns the unique name property for a member of a parent-child dimension in a cube.
  • The member has no parent in the parent level of the parent-child dimension.
  • You use the unique name property of that member to run a second MDX query.
In this scenario, the second MDX query returns incorrect results. The query does not return the member that is queried by the unique name property.

CAUSE

This problem occurs because of a bug in the parser in SQL Server 2005 Analysis Services.

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

After you apply this hotfix, you do not have to restart the computer if the following conditions are true:
  • If Analysis Services is running as a named instance, you stop the SQL Server Browser service before you apply this hotfix.
  • You exit all Analysis Services tools and all client applications before you apply this hotfix.
  • You exit Microsoft Internet Information Services (IIS) before you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.SQL Server 2005, 32-bit
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.smo9.0.1532.01,559,25610-Mar-200601:21Not Applicable
Msmdlocal.dll9.0.1532.015,590,61610-Mar-200601:21Not Applicable
Msmdpump.dll9.0.1532.03,913,94410-Mar-200601:21Not Applicable
Msmdspdm.dll9.0.1532.0154,32810-Mar-200601:20Not Applicable
Msmdsrv.exe9.0.1532.014,569,17610-Mar-200601:21Not Applicable
Msmgdsrv.dll9.0.1532.05,935,83210-Mar-200601:21Not Applicable
Msmgdsrv.dll9.0.1532.05,935,83210-Mar-200601:21Not Applicable
Msolap90.dll9.0.1532.04,204,76010-Mar-200601:21Not Applicable
Sbmsmdlocal.dll9.0.1532.015,590,61610-Mar-200601:21Not Applicable
Sbmsmdredir.dll9.0.1532.03,927,25610-Mar-200601:21Not Applicable

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

MORE INFORMATION

For more information about software update terminology, 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:MajorLast Reviewed:9/19/2006
Keywords:ATdownload kbsql2005sp1fix kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB914597 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.