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

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

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.

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

Hotfix information

A 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: 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.

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  (http://support.microsoft.com/kb/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

SQL Server 2005 hotfix, 64-bit

SQL Server 2005 hotfix, 64-bit for Itanium processors

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.

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

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: