FIX: Use of the Colon Operator to Define a Range of Members May Cause Incorrect Results in MDX Query

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q293195

BUG #: 11928 (plato7x) BUG #: 11998 (plato7x)

SYMPTOMS

When you run a Multidimensional Expressions (MDX) query and you use the Member clause to define virtual levels, and you use the colon operator to define a range for the virtual levels, you may receive incorrect results from the MDX query.

Back to the top

RESOLUTION

RESOLUTION To resolve this problem, obtain the latest service pack for the Microsoft SQL Server 2000 (the Analysis Services Components - Sql2kasp1.exe). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 (http://support.microsoft.com/kb/290211/EN-US/ ) INF: How to Obtain the Latest SQL Server 2000 Service Pack

Back to the top

Hotfix

NOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 1.

The English version of this fix should have the following file attributes or later:

   Date      Time   Version   Size       File name   
   -------------------------------------------------

   3/8/2001  8:37p  8.0.2.65    209,472  Msmdcb80.dll
   3/8/2001  8:37p  8.0.2.65  1,360,448  Msmdgd80.dll
   3/8/2001  8:37p  8.0.2.65  1,733,180  Msmdsrv.exe
   3/832001  8:37p  8.0.2.65  1,983,056  Msolap80.dll
   3/8/2001  8:37p  8.0.2.65    213,067  Msolap80.rll

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.

Back to the top

WORKAROUND

To work around this issue, increase the size of the Large Level Threshold property on the connection string of the client application. For example:

Provider=MSOLAP;Integrated Security=SSPI;Persist Security Info=False;Data Source=MyServer;Initial Catalog=FoodMart 2000;Client Cache Size=25;Auto Synch Period=10000;Large Level Threshold=10000

The value may vary depending on the size of the query, so you may want to start at a value of 10000.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in SQL Server 2000 Analysis Services version 8.0. This problem was first corrected in the Analysis Services Components of Microsoft SQL Server 2000 Service Pack 1.

Back to the top

MORE INFORMATION

Here is sample syntax for a MDX query that generates incorrect results.

With  member [Time Monthly by Day].Total AS 'AGGREGATE({ [Time Monthly by Day].[2000].[Quarter 4].[December].[23] : [Time Monthly by Day].[2001].[Quarter 1].[January].[22] })'

member [Delivery Time].[0-10] AS 'AGGREGATE({ [Delivery Time].[0].[0].[0] : [Delivery Time].[1].[1].[10] })' 
member [Delivery Time].[11-20] AS 'AGGREGATE({ [Delivery Time].[1].[1].[11] : [Delivery Time].[1].[1].[20] })'  
member [Delivery Time].[21-30] AS 'AGGREGATE({ [Delivery Time].[1].[1].[21] : [Delivery Time].[1].[1].[30] })' 
member [Delivery Time].[31+] AS 'AGGREGATE({ [Delivery Time].[1].[1].[31] : [Delivery Time].[11].[601].[36000] })' 
member [Delivery Time].[Total] AS '[Delivery Time].[All Delivery Time]'

Select {[Delivery Time].[31+] } on columns,
{[Measures].[Bytes]} on Rows
from [Cube]
Where ( [Time Monthly by Day].Total, [Servers].[All Servers] )

Back to the top

APPLIES TO

Microsoft SQL Server 2000 Analysis Services

Back to the top

kbbug kbfix kbqfe kbsqlserv2000sp1fix KB293195

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top