FIX: You obtain inconsistent results when you run an MDX query that uses the Siblings function against an instance of SQL Server 2005 Analysis Services compared to an instance of SQL Server 2000 Analysis Services

Article ID: 938748 - View products that this article applies to.
Bug #: 50001184 (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 2005 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the 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
Back to the top | Give Feedback

SYMPTOMS

Consider the following scenario. You use a connection string to connect to an instance of Microsoft SQL Server 2005 Analysis Services. You set the value of the MDX COMPATIBILITY connection string property to 2. Then, you run a Multidimensional Expressions (MDX) query that uses the Siblings function. In this scenario, the result that you obtain is inconsistent with the result that you obtain when you run the same query against an instance of SQL Server 2000 Analysis Services. This problem occurs if the following conditions are true:
  • The member of which you call the Siblings function is on a specific dimension level.
  • The dimension level contains members that are hidden.
Note When you set the value of the MDX COMPATIBILITY connection string property to 2, SQL Server 2005 Analysis Services hides the members that are hidden.
Back to the top | Give Feedback

RESOLUTION

Update information

This hotfix is included in the cumulative hotfix package (build 3175) for SQL Server 2005 Service Pack 2 (SP2). To resolve the problem that is described in this article, install SQL Server 2005 SP2. Then, install the cumulative hotfix package (build 3175) for SQL Server 2005 SP2. For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/913089/ )
How to obtain the latest service pack for SQL Server 2005
For more information about the cumulative hotfix package (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:
936305
(http://support.microsoft.com/kb/936305/ )
Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 SP2 installed to apply this hotfix.

Restart information

You do not have to restart the computer.

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 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 Analysis Services, 32-bit version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200715:05x86
Microsoft.datawarehouse.dll9.0.3175.01,279,34414-Jun-200715:05x86
Msadomdx.dll9.0.3175.0502,64014-Jun-200715:05x86
Msmdlocal.dll9.0.3175.015,948,14414-Jun-200715:05x86
Msmdspdm.dll9.0.3175.0202,09614-Jun-200715:05x86
Msmdsrv.exe9.0.3175.014,916,46414-Jun-200715:05x86
Msmgdsrv.dll9.0.3175.06,045,55214-Jun-200715:05x86
Msolap90.dll9.0.3175.04,299,12014-Jun-200714:05x86

SQL Server 2005 Analysis Services, x64-based version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200714:05x86
Microsoft.datawarehouse.dll9.0.3175.01,279,34414-Jun-200714:05x86
Msadomdx.dll9.0.3175.0502,64014-Jun-200714:05x86
Msmdlocal.dll9.0.3175.015,948,14414-Jun-200714:05x86
Msmdlocal.dll9.0.3175.032,184,68814-Jun-200716:41x64
Msmdspdm.dll9.0.3175.0202,09614-Jun-200716:41x86
Msmdsrv.exe9.0.3175.031,573,36014-Jun-200716:41x64
Msmgdsrv.dll9.0.3175.06,045,55214-Jun-200714:05x86
Msmgdsrv.dll9.0.3175.09,803,12014-Jun-200716:41x64
Msolap90.dll9.0.3175.04,299,12014-Jun-200714:05x86
Msolap90.dll9.0.3175.05,928,81614-Jun-200716:41x64

SQL Server 2005 Analysis Services, Itanium architecture version

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.analysisservices.dll9.0.3175.01,217,90414-Jun-200715:05x86
Microsoft.datawarehouse.dll9.0.3175.01,279,34414-Jun-200715:05x86
Msadomdx.dll9.0.3175.0502,64014-Jun-200715:05x86
Msmdlocal.dll9.0.3175.015,948,14414-Jun-200714:05x86
Msmdlocal.dll9.0.3175.049,904,49614-Jun-200719:56IA-64
Msmdspdm.dll9.0.3175.0202,09614-Jun-200719:56x86
Msmdsrv.exe9.0.3175.048,855,40814-Jun-200719:56IA-64
Msmgdsrv.dll9.0.3175.06,045,55214-Jun-200714:05x86
Msmgdsrv.dll9.0.3175.013,169,00814-Jun-200719:56IA-64
Msolap90.dll9.0.3175.04,299,12014-Jun-200714:05x86
Msolap90.dll9.0.3175.07,908,72014-Jun-200719:56IA-64
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

REFERENCES

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/ )
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 938748 - Last Review: October 12, 2007 - Revision: 2.3
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
Keywords: 
kbautohotfix kbsql2005as kbsql2005bi kbhotfixserver kbexpertiseadvanced kbqfe kbfix KB938748
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top