FIX: Incorrect Results Occur with Write Back of Different Data Types (308955)



The information in this article applies to:

  • Microsoft SQL Server 2000 Analysis Services

This article was previously published under Q308955
BUG #: 12268 (Plato7x)

SYMPTOMS

If you use the writeback method to write back to an Analysis Services cube that has a measure stored as a specific data type such as double or currency and you also update the cube with a different data type such as integer, you may experience incorrect results when you query the cube, after the write back.

For example, the following Multidimensional Expression (MDX) statement updates a cube with the value of 200000, which is an integer value. This produces incorrect results for any MDX query that you run after the update or write back, because the measure Budget Dollars expects a currency data type, such as 200000.00.
UPDATE CUBE [Budget] SET ( [Measures].[Budget Dollars],
 [Time].[Year].&[2000], [Product Line].[All Product Line],
 [Customer].[Country].&[Canada].&[Cliffside] ).VALUE = 200000 
USE_WEIGHTED_ALLOCATION BY ( Cousin( [Time].CurrentMember, 
[Time].[Year].&[1999] ), [Product Line].CurrentMember, 
[Customer].CurrentMember ) / ( [Time].[Year].&[1999], [Product Line].[All 
Product Line], [Customer].[Country].&[Canada].&[Cliffside] ) 
				

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000 Analysis Services. 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

WORKAROUND

To work around this problem, always use the same data type that is stored in the cube for the specific measure that you update.

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

Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB308955