You are modifying a SQL Server Analysis Services (SSAS) cube.
Users of the cube report that the precision for the TransactionCost measure is five digits.
You need to ensure that the TransactionCost measure stores values to two digits of
precision.
What should you do?
A.
Use the FormatString measure property to format TransactionCost as Currency.
B.
Add a named calculation in the data source view that casts the data source column to two
digits of precision. Bind the TransactionCost measure to the new column.
C.
Add a named query in the data source view that casts the data source column to two
digits of precision. Bind the TransactionCost measure to the new query.
D.
Use the MeasureExpression measure property to change the precision of
TransactionCost to two digits.
E.
Use the FormatString measure property to format TransactionCost as #, ##0.00;-#,##0.00.
Answer is C. A named calculation does not store the value of the measure in the cube, but just stores the definition of the calculation.
https://msdn.microsoft.com/en-us/library/ms166568%28v=sql.120%29.aspx
“B”
You write about named calculation IN THE CUBE.
In “B” they mention named calculation in DATA SOURCE VIEW. We will query the datasource and we will receive bigger precision for TransactionCost, but we will replace it immediately by 2 digit expression. Every value starting at this point will have precision of 2 digits, so also everyting saved in the cube will have 2 digits precision.