Microsoft KB Archive/821463

= FIX: Pending Writeback May Cause Results That Are Not Accurate =

Article ID: 821463

Article Last Modified on 11/21/2006

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-



BUG #: 14038 (Plato7x)



SYMPTOMS
When you run a multidimensional expressions (MDX) query on a client application that has a pending writeback transaction, the results returned by the MDX statement may not accurately reflect the pending writeback values. Additionally, functions that are not valid if there is a pending writeback, such as NonEmptyCrossjoin, may be permitted in the MDX query.



MORE INFORMATION
Analysis Services permits clients to analyze different scenarios by using temporary writeback operations. These temporary writeback operations are only visible to the clients that perform them. The pending writeback values are stored in the client memory, and they are used as part of the data results in subsequent queries to show how the changes may affect the cube values. Because the pending writeback values are not sent to the server that is running Analysis Services, queries that are sent to the server that is running Analysis Services for resolution may not:
 * Reflect the pending changes in the data results.
 * Restrict queries to only operations that are valid with pending writeback operations.

This update detects pending writeback operations on the client. If there are any pending writeback operations, the update prevents the client from sending queries to the server that is running Analysis Services.



Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional 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-May-2003 06:14  8.0.806.0         217,668  Msmdcb80.dll 23-Jul-2003 04:23  8.0.0.843       4,055,616  Msmddo80.dll 13-May-2003 06:14  8.0.767.0       1,024,576  Msmdgd80.dll 16-May-2003 08:26  8.0.823.0         172,608  Msmdpump.dll 13-May-2003 06:14  8.0.0.761       9,638,464  Msmdsgn80.dll 22-Jul-2003 23:03  8.0.843.0       1,831,492  Msmdsrv.exe 27-Jun-2003 19:06  8.0.838.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 the previous files may also contain additional files.

SQL Server 2000 Analysis Services 64-bit
For additional information about a hotfix for this problem in the 64-bit version of SQL Server 2000 Analysis Services, click the following article number to view the article in the Microsoft Knowledge Base:

822672 FIX: Hotfix Information for Build 8.0.843.0 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 &quot;Applies to&quot; section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.



MORE INFORMATION
For additional 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 kbqfe kbsqlserv2000presp4fix kbfix kbbug KB821463

-

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

© Microsoft Corporation. All rights reserved.