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

Article translations Article translations
Article ID: 940129 - View products that this article applies to.
Bug #: 50001324 (SQL Hotfix)
Notice
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

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

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.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80113-Jun-200701:18Not applicable
As90.xslNot applicable18,29113-Jun-200701:18Not applicable
Db2v0801.xslNot applicable29,49713-Jun-200701:18Not applicable
Microsoft.analysisservices.dll9.0.3182.01,217,90410-Jul-200704:56x86
Microsoft.datawarehouse.dll9.0.3182.01,279,34410-Jul-200704:56x86
Msadomdx.dll9.0.3182.0502,64010-Jul-200704:56x86
Msjet.xslNot applicable28,51913-Jun-200701:18Not applicable
Msmdlocal.dll9.0.3182.015,948,14410-Jul-200704:56x86
Msmdspdm.dll9.0.3182.0202,09610-Jul-200704:56x86
Msmdsrv.exe9.0.3182.014,916,97610-Jul-200704:56x86
Msmgdsrv.dll9.0.3182.06,045,55210-Jul-200704:56x86
Msolap90.dll9.0.3182.04,299,12010-Jul-200704:56x86
Orcl7.xslNot applicable32,05813-Jun-200701:18Not applicable
Sql2000.xslNot applicable33,62113-Jun-200701:18Not applicable
Sql70.xslNot applicable31,69913-Jun-200701:18Not applicable
Sql90.xslNot applicable38,95313-Jun-200701:18Not applicable
Trdtv2r41.xslNot applicable26,91413-Jun-200701:18Not applicable
SQL Server 2005 Analysis Services, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80113-Jun-200701:18Not applicable
As90.xslNot applicable18,29113-Jun-200701:18Not applicable
Db2v0801.xslNot applicable29,49713-Jun-200701:18Not applicable
Microsoft.analysisservices.dll9.0.3182.01,217,90410-Jul-200704:56x86
Microsoft.datawarehouse.dll9.0.3182.01,279,34410-Jul-200704:56x86
Msadomdx.dll9.0.3182.0502,64010-Jul-200704:56x86
Msjet.xslNot applicable28,51913-Jun-200701:18Not applicable
Msmdlocal.dll9.0.3182.032,184,68810-Jul-200707:51x64
Msmdlocal.dll9.0.3182.015,948,14410-Jul-200704:56x86
Msmdspdm.dll9.0.3182.0202,09610-Jul-200707:51x86
Msmdsrv.exe9.0.3182.031,572,84810-Jul-200707:51x64
Msmgdsrv.dll9.0.3182.09,802,60810-Jul-200707:51x64
Msmgdsrv.dll9.0.3182.06,045,55210-Jul-200704:56x86
Msolap90.dll9.0.3182.05,928,81610-Jul-200707:51x64
Msolap90.dll9.0.3182.04,299,12010-Jul-200704:56x86
Orcl7.xslNot applicable32,05813-Jun-200701:18Not applicable
Sql2000.xslNot applicable33,62113-Jun-200701:18Not applicable
Sql70.xslNot applicable31,69913-Jun-200701:18Not applicable
Sql90.xslNot applicable38,95313-Jun-200701:18Not applicable
Trdtv2r41.xslNot applicable26,91413-Jun-200701:18Not applicable
SQL Server 2005 Analysis Services, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
As80.xslNot applicable16,80113-Jun-200701:18Not applicable
As90.xslNot applicable18,29113-Jun-200701:18Not applicable
Db2v0801.xslNot applicable29,49713-Jun-200701:18Not applicable
Microsoft.analysisservices.dll9.0.3182.01,217,90410-Jul-200704:56x86
Microsoft.datawarehouse.dll9.0.3182.01,279,34410-Jul-200704:56x86
Msadomdx.dll9.0.3182.0502,64010-Jul-200704:56x86
Msjet.xslNot applicable28,51913-Jun-200701:18Not applicable
Msmdlocal.dll9.0.3182.049,907,05610-Jul-200713:01IA-64
Msmdlocal.dll9.0.3182.015,948,14410-Jul-200704:56x86
Msmdspdm.dll9.0.3182.0202,09610-Jul-200713:01x86
Msmdsrv.exe9.0.3182.048,857,45610-Jul-200713:01IA-64
Msmgdsrv.dll9.0.3182.013,168,49610-Jul-200713:01IA-64
Msmgdsrv.dll9.0.3182.06,045,55210-Jul-200704:56x86
Msolap90.dll9.0.3182.07,908,72010-Jul-200713:01IA-64
Msolap90.dll9.0.3182.04,299,12010-Jul-200704:56x86
Orcl7.xslNot applicable32,05813-Jun-200701:18Not applicable
Sql2000.xslNot applicable33,62113-Jun-200701:18Not applicable
Sql70.xslNot applicable31,69913-Jun-200701:18Not applicable
Sql90.xslNot applicable38,95313-Jun-200701:18Not applicable
Trdtv2r41.xslNot applicable26,91413-Jun-200701:18Not applicable

WORKAROUND

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.

STATUS

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

MORE INFORMATION

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:
http://msdn2.microsoft.com/en-us/library/ms345116.aspx
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:
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: 940129 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Analysis Services
Keywords: 
kbautohotfix kbsql2005as kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB940129

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