Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: You may receive incorrect results when you run a Multidimensional Expressions (MDX) query and the WHERE clause and the SELECT clause in the query contain different attributes of the same dimension in SQL Server 2005 Analysis Services
Article ID: 936968 - View products that this article applies to.
Bug #: 500001122 (SQL Hotfix)
When you run a Multidimensional Expressions (MDX) query in Microsoft SQL Server 2005 Analysis Services, you may receive incorrect results. This problem occurs when the following clauses in the query contain different attributes of the same dimension:
This problem occurs because the attributes are incorrectly overwritten when you run the MDX query.
Cumulative update informationThe fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/936305/LN/ )Cumulative update package 2 for SQL Server 2005 Service Pack 2
937137Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/ )The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Steps to reproduce the problem