FIX: UPDATE CUBE Statement Allocates Data Incorrectly (308959)

The information in this article applies to:

Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q308959

BUG #: 12604 (Plato7x)

SYMPTOMS

When you issue an UPDATE CUBE statement using either the USE_WEIGHTED_INCREMENT or USE_WEIGHTED_ALLOCATION method, the results do not sum to the value specified in the UPDATE CUBE statement, and the data is not allocated as would be expected.

CAUSE

This behavior occurs due to a rounding error.

RESOLUTION

To resolve this problem, obtain the latest service pack for 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

STATUS

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 SQL Server 2000 Service Pack 2.

MORE INFORMATION

When you issue an UPDATE CUBE statement using the USE_WEIGHTED_ALLOCATION method, every atomic cell that contributes to the updated cell is assigned an equal value which is expressed as follows:

atomic cell value = value * weight value expression

When you issue an UPDATE CUBE statement using the USE_WEIGHTED_INCREMENT method, every atomic cell that contributes to the updated cell will be changed according to the following formula:

atomic cell value = atomic cell value + (value - existing value) * weight value expression

Modification Type:	Major	Last Reviewed:	6/30/2004
Keywords:	kbbug kbpending KB308959