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
Bug #: 50000923 (SQL Hotfix) NoticeMicrosoft 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.On This PageSUMMARY
This article describes the following about this hotfix release:
SYMPTOMSWhen 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:
CAUSEThis 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: RESOLUTIONCumulative update informationTo 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 (http://support.microsoft.com/kb/936305/)
Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
Hotfix informationA 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.PrerequisitesYou 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 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis 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, x86-based version
SQL Server 2005, x64-based version
SQL Server 2005, Itanium architecture version
WORKAROUNDTo 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. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" 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 (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
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
