FIX: An MDX query does not return results when you execute the query against a cube that contains an unnatural hierarchy in a dimension in SQL Server 2005 Analysis Services

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

In Microsoft SQL Server 2005 Analysis Services, you have a cube that contains an unnatural hierarchy in a dimension. When you execute a Multidimensional Expressions (MDX) query against the cube and reference the hierarchy, the query unexpectedly does not return results. However, if you use the NON EMPTY keyword in the query, the query returns results as expected.

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 2
  
  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 information

You do not have to restart the computer after you apply this hotfix. However, this hotfix stops and then restarts the Analysis Services service. If you have configured Analysis Services for HTTP access, you must stop Internet Information Services (IIS) and then restart it after the installation is complete. If you have installed Analysis Services as a named instance, you must stop the SQL Server Browser service because the Msmdredir.dll component of the SQL Server Browser service is updated when you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any other hotfixes.

Registry information

You do not have to change the registry.

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 Analysis Services, 32-bit version

SQL Server 2005 Analysis Services, x64-based version

SQL Server 2005 Analysis Services, Itanium architecture version

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

• If it is possible, do not use unnatural hierarchies.
• Use the NON EMPTY keyword in the query.

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

You can use the NON EMPTY keyword to work around this problem.

Analysis Services cannot use "dimension cube" to determine which members have data. Therefore, Analysis Services must query the data in the actual cube.

For more information about natural and unnatural hierarchies, visit the following Microsoft Developer Network (MDSN) Web site: 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: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: