FIX: Queries Return Empty Result Sets If a Calculated Member Is Defined by Using the NonEmptyCrossjoin Function

Article translations Article translations
Article ID: 830393 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 14158 (Plato7x)
Expand all | Collapse all

On This Page

SYMPTOMS

When a calculated member is defined by using the NonEmptyCrossjoin function, queries that involve the calculated member may incorrectly return an empty result set. This problem occurs when the following conditions are true:
  • One of the axes in the query contains only the calculated member and no base members.
  • The calculated member does not invoke a set traversal function (such as SUM, MIN, MAX, AGGREGATE, FILTER, ORDER, or GENERATE) on members of the dimension where the calculated member is defined.
  • No other calculation in the query invokes a set traversal function on members of the dimension where the calculated member is defined.
  • There are one or more additional calculations in the query that uses either the NonEmptyCrossjoin function or the DistinctCount function, and the calculation is applied before the calculated member definition.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

Hotfix information


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 tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   13-Sep-2003  22:50  8.0.806.0         217,668  Msmdcb80.dll     
   13-Sep-2003  22:50  8.0.0.843       4,055,616  Msmddo80.dll     
   27-Sep-2003  03:02  8.0.864.0       1,032,768  Msmdgd80.dll     
   13-Sep-2003  22:50  8.0.823.0         172,608  Msmdpump.dll     
   27-Sep-2003  03:02  8.0.0.864       9,638,468  Msmdsgn80.dll    
   03-Oct-2003  21:08  8.0.868.0       1,835,588  Msmdsrv.exe      
   03-Oct-2003  21:08  8.0.868.0       2,077,264  Msolap80.dll     
   10-May-2003  08:05  8.0.820.0         213,069  Msolap80.rll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

SQL Server 2000 Analysis Services 64-bit

For more information about a hotfix build that was designed for a server that is running SQL Server 2000 Analysis Services 64-bit or to find out if a fix is scheduled to be included in SQL Server 2000 Analysis Services 64-bit Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
825804 FIX: Hotfix information for build 8.0.872 of SQL Server 2000 Analysis Services 64-bit


STATUS

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

This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

REFERENCES

For more information, 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: 830393 - Last Review: February 27, 2014 - Revision: 3.3
APPLIES TO
  • Microsoft SQL Server 2000 Analysis Services
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbsqlserv2000presp4fix kbfix kbbug KB830393

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