You are modifying a SQL Server Analysis Services (SSAS) cube. Users in the cube report that the precision for the TransactionCost measure is five digits. You need to ensure that the TransactionCost…

Question

Options

• AAdd 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.
• BAdd 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.
• CUse the FormatString measure property to format TransactionCost as #.##;0.00;-.#.##;0.00.
• DUse the FormatString measure property to format TransactionCost as Currency.
• EUse the MeasureExpression measure property to change the precision of TransactionCost to two digits.

• A
  73% (19)
• B
  8% (2)
• D
  15% (4)
• E
  4% (1)

Explanation

To change the actual stored precision of a measure (not just its display format), you must alter the data values before they are loaded into SSAS. A named calculation in the Data Source View (DSV) lets you define a computed column using a SQL expression such as CAST or ROUND applied to the source column, effectively truncating the value to two decimal places at the data layer. You then rebind the TransactionCost measure to this new named calculation column so SSAS stores the rounded values. Option B (named query) replaces an entire table with a SQL query and is heavier than necessary for a single column change. Options C and D use FormatString, which only affects how values are displayed to end users - it does not change the underlying stored precision. Option E (MeasureExpression) is used for weighted or semi-additive aggregations, not for controlling numeric precision.

No community discussion yet for this question.