Microsoft KB Archive/926235

= FIX: In SQL Server 2005 Analysis Services, the query may not return all the expected rows when you use the TopCount function in an MDX query =

Article ID: 926235

Article Last Modified on 11/4/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



Bug #: 50000317 (SQL Hotfix)



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.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for applying the hotfix package
 * Whether you must restart the computer after you apply the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes after you apply the hotfix package
 * The files that are contained in the hotfix package



SYMPTOMS
When you use the TopCount function in a Multidimensional Expressions (MDX) query in Microsoft SQL Server 2005 Analysis Services, the query may not return all the expected rows. This problem occurs after you apply hotfix build 9.00.2185.

For example, the following query does not return all the rows when you run this query against the AdventureWorks sample database in Analysis Services. WITH SET [RowSet0] AS {[Sales Territory].[Sales Territory Country].[All Sales Territories].children} SET [RowSet1] AS topcount([RowSet0],100)

SELECT {[Date].[Fiscal].[Fiscal Year].&[2005]} ON COLUMNS, CROSSJOIN({[Sales Territory].[Sales Territory Country].[All Sales Territories], [RowSet1]},{[Measures].[Internet Sales Amount]}) ON ROWS FROM [Adventure Works] WHERE ([Sales Territory].[Sales Territory Group].&[Europe])



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
 Microsoft SQL Server 2005 Service Pack 1 (SP1)

For information about how to obtain SQL Server 2005 SP1, 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
If the installer must replace files that are being used, you must restart the computer. To avoid restarting the computer, exit all Analysis Services tools and all Analysis Services clients. If the server is configured to provide HTTP access, you must exit Microsoft Internet Information Services (IIS). If you installed Analysis Services as a named instance, you must stop the SQL Server Browser service.

Registry information
You do not have to change the registry.

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


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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

Keywords: kbhotfixserver kbqfe kbpubtypekc KB926235

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.