Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: Query Results Are Not Correct After You Perform an Incremental Update of a Changing Dimension and a Virtual Dimension
Article ID: 821104 - View products that this article applies to.
Bug #: 14036 (Plato 7x)
If you perform an incremental update of a changing dimension and a virtual dimension that depends on that changing dimension, you may receive query results that are not correct. This problem may occur if both the following conditions are true:
Service pack informationTo 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:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe 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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Date Time Version Size File name ---------------------------------------------------------- 13-May-2003 06:14 8.0.806.0 217,668 Msmdcb80.dll 23-Jul-2003 04:23 184.108.40.2063 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 220.127.116.111 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
To work around this problem, rebuild the dimension structure, and then perform a full process of the cube.
Microsoft 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 4.