Microsoft KB Archive/935829

= FIX: You receive incorrect results when you run an MDX query against a dimension that contains a parent-child hierarchy in SQL Server 2005 Analysis Services =

Article ID: 935829

Article Last Modified on 11/4/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



Bug #: 50000923 (SQL Hotfix)



Notice
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
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you run a Multidimensional Expressions (MDX) query in SQL Server 2005 Analysis Services, you receive incorrect results. This problem occurs if the following conditions are true:
 * You run an MDX query against a dimension that contains a parent-child hierarchy.
 * The dimension is stored by using the Relational OLAP (ROLAP) mode.
 * The hierarchy has multiple levels of slice members.



CAUSE
This problem occurs because the MDX query uses the Sql90.xsl data cartridge to generate an incorrect dimension subquery. The subquery uses a common table expression (CTE) to retrieve the descendants recursively. The members of the hierarchy are duplicated in the subquery. Therefore, values are double counted in the top level of the MDX query.

For example, you run an MDX query that involves three slice members. The three slice members are named M1, M2, and M3. M1 is the parent of M2 and M3. If you use the Sql2000.xsl data cartridge instead of the Sql90.xsl data cartridge, SQL Server 2005 Analysis Services generates a dimension subquery that does not use CTE when you run the MDX query. In this example, the subquery returns the following result: { M1, M2, M3 } However, if you use the Sql90.xsl data cartridge for the MDX query, SQL Server 2005 Analysis Services generates a dimension subquery that uses CTE. The subquery returns the following result: { M1, M2, M3, M2, M3 } Therefore, the values of M2 and M3 are counted two times at the top level of the MDX query.



Cumulative update information
To resolve this problem, obtain cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). For more information about how to obtain cumulative update package 2 (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 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 Service Pack 2 (SP2) installed to apply this hotfix.

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

Restart information
You do not have to restart the computer after you apply 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.

SQL Server 2005, Itanium architecture version


WORKAROUND
To work around this problem, do not use the SQL Server 2005 cartridge (Sql90.xsl). If you delete the Sql90.xsl cartridge, the SQL Server 2000 cartridge (Sql2000.xsl) is used instead.



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



MORE INFORMATION
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 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 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbsql2005as kbexpertiseadvanced kbfix kbpubtypekc kbqfe kbhotfixserver KB935829

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.