FIX: A query may return incorrect results when you run the query against a SQL Server 2005 Analysis Services cube (920340)


The information in this article applies to:

  • Microsoft SQL Server 2005 Analysis Services
Bug #: 440398 (SQLBUDT)
Bug #: 861 (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 run a query against a Microsoft SQL Server 2005 Analysis Services cube.
  • The cube contains a dimension.
  • The dimension contains multiple user-defined hierarchies.
In this scenario, the query may return incorrect results. This problem occurs if the following conditions are true:
  • The multiple user-defined hierarchies have at least two attributes in common.

    Note This problem does not occur if the multiple user-defined hierarchies have the All member and only one other attribute in common.
  • The attribute relationships are defined so that each hierarchy has a different relationship path between the two attributes in common.
  • The query retrieves data from an intermediate aggregation, and then the intermediate aggregation is aggregated again to solve the query.

CAUSE

This problem occurs because of a bug in the Analysis Services storage engine.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may 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 immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

  • SQL Server 2005 Service Pack 1 (SP1)

    For more information about how to obtain SQL Server 2005 Service Pack 1, 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

After you apply this hotfix, you do not have to restart the computer if the following conditions are true:
  • If Analysis Services is running as a named instance, you stop the SQL Server Browser service before you apply this hotfix.
  • You exit all Analysis Services tools and all client applications before you apply this hotfix.
  • You exit Microsoft Internet Information Services (IIS) before you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 hotfix, 32-bit
File nameFile versionFile sizeDateTimePlatform
Cu.datawarehouse.dll9.0.2176.01,276,70425-Jul-200614:22Not Applicable
Adomdclient.dll9.0.2176.0543,52025-Jul-200614:20Not Applicable
Microsoft.analysisservices.9.0.2176.01,215,26425-Jul-200614:22Not Applicable
Microsoft.sqlserver.sqlenum9.0.2176.0908,06425-Jul-200614:22Not Applicable
Ms.as.deployengine.dll9.0.2176.0138,01625-Jul-200614:19Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2176.075,55225-Jul-200614:18Not Applicable
Msadomdx.dll9.0.2176.0502,56025-Jul-200614:20Not Applicable
Msmdlocal.dll9.0.2176.015,681,82425-Jul-200614:23Not Applicable
Msmdsrv.exe9.0.2176.014,661,92025-Jul-200614:23Not Applicable
Msmgdsrv.dll9.0.2176.05,972,25625-Jul-200614:23Not Applicable
Msolap90.dll9.0.2176.04,249,37625-Jul-200614:23Not Applicable
Sbmsmdlocal.dll9.0.2176.015,681,82425-Jul-200614:23Not Applicable
Sbmsmdredir.dll9.0.2176.03,968,80025-Jul-200614:23Not Applicable
Uc.analysisservices9.0.2176.01,215,26425-Jul-200614:22Not Applicable
SQL Server 2005 hotfix, 64-bit
File nameFile versionFile sizeDateTimePlatform
Cu.datawarehouse.dll9.0.2176.01,276,70425-Jul-200614:22Not Applicable
Adomdclient.dll9.0.2176.0543,52025-Jul-200614:19Not Applicable
Microsoft.analysisservices9.0.2176.01,215,26425-Jul-200614:22Not Applicable
Microsoft.sqlserver.sqlenum9.0.2176.0875,29625-Jul-200614:16Not Applicable
Ms.as.deployengine.dll9.0.2176.0138,01625-Jul-200614:19Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2176.075,55225-Jul-200614:18Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2176.091,42425-Jul-200614:16Not Applicable
Msadomdx.dll9.0.2176.0502,56025-Jul-200614:20Not Applicable
Msmdlocal.dll9.0.2176.015,681,82425-Jul-200614:23Not Applicable
Msmdlocal.dll9.0.2176.030,188,32025-Jul-200614:17Not Applicable
Msmdsrv.exe9.0.2176.029,513,50425-Jul-200614:17Not Applicable
Msmgdsrv.dll9.0.2176.05,972,25625-Jul-200614:23Not Applicable
Msmgdsrv.dll9.0.2176.08,966,94425-Jul-200614:17Not Applicable
Msolap90.dll9.0.2176.04,249,37625-Jul-200614:23Not Applicable
Msolap90.dll9.0.2176.05,737,24825-Jul-200614:17Not Applicable
Sbmsmdlocal.dll9.0.2176.015,681,82425-Jul-200614:23Not Applicable
Sbmsmdredir.dll9.0.2176.03,968,80025-Jul-200614:23Not Applicable
Uc.analysisservices9.0.2176.01,215,26425-Jul-200614:22Not Applicable
SQL Server 2005 hotfix, 64-bit for Itanium processors
File nameFile versionFile sizeDateTimePlatform
Cu.datawarehouse.dll9.0.2176.01,276,70425-Jul-200614:22Not Applicable
Adomdclient.dll9.0.2176.0543,52025-Jul-200614:20Not Applicable
Microsoft.analysisservices9.0.2176.01,215,26425-Jul-200614:22Not Applicable
Microsoft.sqlserver.sqlenum9.0.2176.0875,29625-Jul-200614:15Not Applicable
Ms.as.deployengine.dll9.0.2176.0138,01625-Jul-200614:19Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2176.075,55225-Jul-200614:18Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2176.0163,10425-Jul-200614:14Not Applicable
Msadomdx.dll9.0.2176.0502,56025-Jul-200614:20Not Applicable
Msmdlocal.dll9.0.2176.015,681,82425-Jul-200614:23Not Applicable
Msmdlocal.dll9.0.2176.048,778,01625-Jul-200614:16Not Applicable
Msmdsrv.exe9.0.2176.047,735,07225-Jul-200614:16Not Applicable
Msmgdsrv.dll9.0.2176.05,972,25625-Jul-200614:23Not Applicable
Msmgdsrv.dll9.0.2176.012,909,85625-Jul-200614:16Not Applicable
Msolap90.dll9.0.2176.04,249,37625-Jul-200614:23Not Applicable
Msolap90.dll9.0.2176.07,771,42425-Jul-200614:16Not Applicable
Sbmsmdlocal.dll9.0.2176.048,778,01625-Jul-200614:16Not Applicable
Sbmsmdredir.dll9.0.2176.06,155,04025-Jul-200614:16Not Applicable
Uc.analysisservices9.0.2176.01,215,26425-Jul-200614:22Not Applicable

WORKAROUND

To work around this problem, use one of the following methods:
  • Rewrite the query to make sure that only one attribute relationship path exists.
  • Do not design aggregations on dimensions where multiple attribute relationship paths exist.

STATUS

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

MORE INFORMATION

The following example shows how this problem occurs:
  • Hierarchy 1 contains the following attributes:

    Store / District / Region / Division / Geography / BusinessLine

  • Hierarchy 2 contains the following attributes:

    Store / Market / Marketing Group / Division / Geography / BusinessLine

In this example, each attribute has a relationship with the previous attribute in the hierarchy. The relationships in both hierarchies result in multiple relationship paths. In this example, multiple relationship paths exist from the Store attribute to the BusinessLine attribute.

If a query tries to access the BusinessLine attribute in hierarchy 1, Analysis Services may select an aggregation that exists for an attribute in hierarchy 2. When Analysis Services tries to aggregate along the relationships in hierarchy 2, the query returns incorrect results. The query returns incorrect results because hierarchy 2 does not include the Region attribute.

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

Modification Type:MajorLast Reviewed:8/31/2006
Keywords:kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB920340 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.