Microsoft KB Archive/938748

= 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

Article Last Modified on 10/12/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



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.



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



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.



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 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 Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available

Hotfix information
A supported hotfix is now 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 SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

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, Itanium architecture version


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

