FIX: You receive an incorrect result when you run an MDX query against a dimension that has a parent/child relationship after you install a cumulative update in SQL Server 2005 Analysis Services or in SQL Server 2008 Analysis Services

Article translations Article translations
Article ID: 975783 - View products that this article applies to.
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

SYMPTOMS

Consider the following scenario.
  • You are running one of the following versions of SQL Server:
    • SQL Server 2005 Service Pack 2 (SP2) (version 9.00.3315 to 9.00.3355)
      Affected cumulative update releases:
      • SQL Server 2005 SP2 Cumulative Update 12
      • SQL Server 2005 SP2 Cumulative Update 13
      • SQL Server 2005 SP2 Cumulative Update 14
      • SQL Server 2005 SP2 Cumulative Update 15
      • SQL Server 2005 SP2 Cumulative Update 16
    • SQL Server 2005 Service Pack 3 (SP3) (version 9.00.4220 to 9.00.4265)
      Affected cumulative update releases:
      • SQL Server 2005 SP3 Cumulative Update 3
      • SQL Server 2005 SP3 Cumulative Update 4
      • SQL Server 2005 SP3 Cumulative Update 5
    • The release version of SQL Server 2008 (version 10.00.1787 to 10.00.1822)
      Affected cumulative update releases:
      • SQL Server 2008 Cumulative Update 3
      • SQL Server 2008 Cumulative Update 4
      • SQL Server 2008 Cumulative Update 5
      • SQL Server 2008 Cumulative Update 6
      • SQL Server 2008 Cumulative Update 7
    • SQL Server 2008 Service Pack 1 (SP1) (version 10.00.2531, and 10.00.2710 to 10.00.2742)
      Affected cumulative update releases:
      • SQL Server 2008 SP1
      • SQL Server 2008 SP1 Cumulative Update 1
      • SQL Server 2008 SP1 Cumulative Update 2
      • SQL Server 2008 SP1 Cumulative Update 3
      • SQL Server 2008 SP1 Cumulative Update 4
  • Your Analysis Services database has a parent/child dimension and there is a cube with at least one partition that includes only one member of the key attribute hierarchy of this parent/child dimension.
In this scenario, you may experience the following symptoms
  • Some sequences of queries may result in different results, depending on the order in which they are executed. This occurs if the queries request intersecting slices of data at different levels of detail for the parent/child dimension. Therefore, one query may cause incorrect data to be cached and then used by the other query. Depending on the sequence and the state of the cache, either query (or both queries) may return incorrect results, and the results will depend on the sequence in which the queries were run.
  • In this situation, the automatic partition slice incorrectly eliminates the partition during scans even when data is present in the partition for the member being filtered. Therefore, when there are no calculations, the results will typically contain either NULLs or different values than expected.

RESOLUTION

Use the following table to find the appropriate method to resolve the problem for your version of SQL Server:
Collapse this tableExpand this table
SQL Server releaseAffected cumulative update (version of SQL Server)Resolution
SQL Server 2005 SP29.00.3315 to 9.00.3355Apply SQL Server 2005 SP2 Cumulative Update package 17.
SQL Server 2005 SP39.00.4220 to 9.00.4265Apply SQL Server 2005 SP3 Cumulative Update package 6.
The release version of SQL Server 200810.00.1787 to 10.00.1822Apply SQL Server 2008 Cumulative Update package 8.
SQL Server 2008 SP110.00.2531, 10.00.2710 to 10.00.2742Apply SQL Server 2008 SP1 Cumulative Update package 5.

Cumulative update information

SQL Server 2005 SP3

The fix for this issue was first released in Cumulative Update 6 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
974648 Cumulative update package 6 for SQL Server 2005 Service Pack 3
Note 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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 SP2

The fix for this issue was also released in Cumulative Update 17 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
976952 Cumulative update package 17 for SQL Server 2005 Service Pack 2
Note 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft 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.

The release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
975976 Cumulative update package 8 for SQL Server 2008
Note 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 2008 fix release. We recommend 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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

SQL Server 2008 Service Pack 1

The fix for this issue was also released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
975977 Cumulative update package 5 for SQL Server 2008 Service Pack 1
Note 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 2008 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

WORKAROUND

To work around this problem, use one of the following methods:

Method 1

Disable partition indexing and reprocess the database. To disable partition indexing, set server configuration property IndexBuildEnabled to 0. To do this, follow these steps:
  1. Open the server configuration file Msmdsrv.ini that is located in the following folder:
    C:\Program Files\Microsoft SQL Server\AS Server Instance folder\OLAP\Config
  2. Change the value of IndexBuildEnabled to 0
Method 2
Delete partition indexes by issuing the following XMLA request:
<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2" xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2">
    <Object>
     <DatabaseID>[Your Database ID]</DatabaseID>
     <CubeID>[Your Cube ID]</CubeID>
    </Object>
    <Type>ProcessClearIndexes</Type>
    <WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Batch>
Note Method 1 and method 2 may result in decrease in performance.

Method 3

Add a row to the partition with at least one other member from the parent child dimension. For example, if your partition originally only had data for the parent/child member Account1, then add a record for Account2.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

To know whether the version of SQL Server Analysis Services that is installed on your computer is affected by this problem, check whether the version of the Msmdsrv.exe file matches one of the affected versions in the "Symptoms" section. Generally, the msmdsrv.exe file is in one of the following folders, depending on whether SQL Server is installed by using Windows on Windows (WOW) mode.

C:\Program Files\Microsoft SQL Server\AS Server Instance Folder\OLAP\bin
C:\Program Files (x86)\Microsoft SQL Server\AS Server Instance Folder\OLAP\bin

For more information about how to identify the SQL Server version, click the following article number to view the article in the Microsoft Knowledge Base:
321185 How to identify your SQL Server version and edition

REFERENCES

For more informationabout the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more informationabout how to obtain SQL Server 2005 Service Pack 3, 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 informationabout 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

Properties

Article ID: 975783 - Last Review: November 3, 2009 - Revision: 3.4
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
  • Microsoft SQL Server 2008 Analysis Services
Keywords: 
kbsurveynew kbfix kbqfe kbexpertiseadvanced KB975783

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com