FIX: An Analysis Services Virtual Cube That Is Based on a Real-Time ROLAP Cube Does Not Receive Updates from the Source (324859)
The information in this article applies to:
- Microsoft SQL Server 2000 Analysis Services
This article was previously published under Q324859 BUG #: 12801 (Plato7x) SYMPTOMS When a virtual cube in Analysis Services contains one or
more source cubes that use relational OLAP (ROLAP) storage with real-time
updates, the virtual cube data is not updated when the source table for the
ROLAP source cube (or cubes) is changed.
When you disconnect from the
computer that is running Analysis Services, reconnect, and then re-issue the
query to update the data. CAUSE The Analysis Services client DLL uses caching of query
results to provide faster answers to queries for which the client already has
retrieved data. The client periodically queries the computer that is running
Analysis Services to determine if any of the cubes for which it has cached
results have been changed. If the version number for any of the objects, for
which the client has cached results, has changed, the Analysis Services client
clears the cached results, and then sends any subsequent queries to the
computer that is running Analysis Services.
Before this update, an
update of the version number information for virtual cubes did not occur when
the update for the underlying source cube (or cubes) version information
occurred. As a result, the client did not clear the cache for the virtual cube.
RESOLUTION 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 INF: How To Obtain the Latest SQL Server 2000 Service Pack NOTE: The following hotfix was created before the release of Microsoft
SQL Server 2000 Service Pack 3. The English version of this fix has
the file attributes (or later) 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
------------------------------------------------------------
06-JUN-2002 19:22 PM 8.0.639.0 1,774,148 Msmdsrv.exe
07-JUN-2002 10:36 AM 8.0.639.0 2,024,016 Msolap80.dll
18-APR-2001 01:23 AM 2000.80.382.0 815,676 Sqldata.dll
07-JUN-2002 10:36 AM 2000.80.534.0 590,396 Sqlsort.dll
NOTE: Because of file dependencies, the most recent hotfix or feature
that contains these files may also contain additional files. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
This problem was first corrected in Microsoft SQL Server
2000 Service Pack 3.MORE INFORMATION The frequency of the version checking queries that are sent
to the computer that is running Analysis Services by the client is controlled
with the Auto Synch Period parameter in the connection string. If no Auto Synch Period is specified in the client connection string, by default, the
value uses 10 seconds. For more information, view the "Auto Synch Period" topic
in the Analysis Services Books Online.
Modification Type: | Minor | Last Reviewed: | 7/13/2004 |
---|
Keywords: | kbbug kbfix kbQFE kbSQLServ2000preSP3fix KB324859 |
---|
|