FIX: The Analysis server computer stops responding when you process dimensions and virtual dimensions (840223)

Date         Time   Version            Size    File name
--------------------------------------------------------------
08-Apr-2004  16:32  8.0.931.0         221,760  Msmdcb80.dll     
08-Apr-2004  16:32  8.0.0.931       4,063,808  Msmddo80.dll     
08-Apr-2004  16:32  8.0.931.0       1,032,768  Msmdgd80.dll     
08-Apr-2004  16:32  8.0.931.0         172,608  Msmdpump.dll     
08-Apr-2004  16:32  8.0.0.931       9,638,468  Msmdsgn80.dll    
08-Apr-2004  16:32  8.0.931.0       1,835,588  Msmdsrv.exe      
08-Apr-2004  16:32  8.0.931.0       2,081,360  Msolap80.dll     
08-Apr-2004  02:09  8.0.931.0         213,068  Msolap80.rll

Date         Time   Version            Size    File name
--------------------------------------------------------------
08-Apr-2004  18:24  8.0.931.0       5,492,736  Msmdcb80.dll
08-Apr-2004  18:24  8.0.931.0       5,801,984  Msmdgd80.dll
08-Apr-2004  18:24  8.0.931.0       5,130,752  Msmdpump.dll
08-Apr-2004  18:24  8.0.931.0       5,993,472  Msmdsrv.exe
08-Apr-2004  18:24  8.0.931.0       6,671,360  Msolap80.dll
08-Apr-2004  16:44  8.0.931.0         201,216  Msolap80.rll

MORE INFORMATION

This hotfix includes a fix that addressed an issue that causes the corruption of dimensions when a Lazy Aggregation processing thread is executed after it processes dimensions that are used in virtual dimensions. Because of that fix, if you incrementally process a virtual dimension, a lazy aggregation processing thread executes. While the lazy aggregation thread executes, the aggregations for that dimension are deleted from each partition.

The lazy aggregation thread executes as a low priority background thread and rebuilds the aggregations for the dimension in each partition. While the lazy aggregation thread executes to rebuild the aggregations, MDX query execution may be significantly slower. The degradation in query performance occurs because of the lack of aggregations. The lack of aggregators causes the server to read values from the leaf level of each partition.

After the lazy aggregation thread finishes rebuilding the aggregations for each partition, you no longer see the degradation in query performance. The query performance degradation during lazy aggregation may be unacceptable in certain situations, such as in high-demand cubes in enterprise applications. If applying this hotfix causes unacceptable query performance degradation, we recommend that you consider the following alternatives during lazy aggregation:

• Set the DSOCommitMode registry value to DSOCommitModeNonLazyIndexing. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  325289 FIX: New functionality for incremental update of changing dimensions

  This option can increase memory and disk usage on the Analysis server. Memory usage increases because processing the affected cubes requires additional memory for the processing buffer to recalculate the cube aggregates. Disk usage increases to approximately double the cumulative size of all affected cubes because the new copies of the data and aggregates are created and because the original data is kept for current user queries. Also, the total elapsed time to complete transactions may be considerably longer than with the conventional lazy aggregation process.
• Set the Virtual property and the Changing property of any virtual dimensions to False.
  
  Note If you change these properties, you must fully re-process any cubes that use the changed dimension.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: