Microsoft KB Archive/913848

= FIX: The results that are returned when you query a SQL Server 2005 Analysis Services cube may be incorrect for some members =

Article ID: 913848

Article Last Modified on 7/26/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Analysis Services

-



Bug #: 247 (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 this hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether the hotfix package is replaced by any other hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you query a SQL Server 2005 Analysis Services cube, the results that are returned may be incorrect for some members.

This problem occurs when the cube has a distinct count measure.

Note A distinct count measure is a measure that has an Aggregate Function property value set to Distinct Count.



CAUSE
This problem occurs because the following conditions are true:
 * The measure group that contains the distinct count measure is stored in more than one partition.
 * The Analysis Services storage engine skips a segment of data from the second partition.



Service pack information
To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, 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

Hotfix information
SQL Server 2005 Analysis Services service packA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 Analysis Services service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
There are no prerequisites for this hotfix.

Restart information
You may have to restart the computer after you apply this hotfix when all the following conditions are true:
 * The instance of SQL Server 2005 Analysis Services that is updated is a named instance.
 * The SQL Server Browser service is not stopped before you apply the hotfix.

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 of 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 32-bit hotfix


WORKAROUND
To work around this problem, redesign the storage for the measure group that contains the distinct count measure. When you do this, configure the measure group to be stored in only one partition.

Note The viability and effect of this workaround will depend on the quantity of data that is stored, the available memory, and the disk space requirements.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was corrected in SQL Server 2005 Analysis Services Service Pack 1.



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

Additional query words: OLAP

Keywords: atdownload kbsql2005sp1fix kbbug kbfix kbtshoot kbdesign kbhotfixserver kbqfe kbpubtypekc KB913848

-

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

© Microsoft Corporation. All rights reserved.