Which technique is most likely to improve query performance?

Question

Options

• ASet the auto-sort property to maximum.
• BSet the detail aggregation to 'Calculated' for measures.
• CAvoid functions in filters.
• DAdd more joins between queries.

• A
  27% (8)
• B
  50% (15)
• C
  10% (3)
• D
  13% (4)

Explanation

Setting detail aggregation to 'Calculated' for measures pushes the aggregation logic down to the database engine, allowing the database to return pre-summarized results rather than returning large volumes of row-level detail data to be aggregated in the reporting layer - this dramatically reduces data transfer and processing overhead.

Why the distractors are wrong:

• A (Auto-sort): Sorting properties affect how results are displayed or ordered after retrieval, not how efficiently the underlying query executes - it adds processing, not removes it.
• C (Avoid functions in filters): While avoiding functions on filtered columns is a valid SQL optimization (it prevents index usage), it is a narrow, situational improvement compared to the broad gains from changing aggregation strategy, making it less universally impactful.
• D (More joins): Adding joins increases query complexity, multiplies the rows the engine must reconcile, and almost always hurts performance rather than helping it.

Memory tip: Think of it as "do the math early." Setting aggregation to 'Calculated' means the database does the heavy lifting before sending results back - less data traveling through the pipeline means a faster query end-to-end.

No community discussion yet for this question.