A developer is troubleshooting a slow multi-join query and opens its Query Profile to find which step is consuming the most resources. They want to pinpoint the single operator that is the most expensive so they can target their tuning effort there. Which feature of Query Profile should they rely on to find it?
- AThe query id displayed in the profile header, which encodes the slowest operator in its suffix so the expensive step can be decoded directly from the id
- BThe warehouse size badge on the profile, which turns red on the operator that spilled so the slowest step is always the one flagged by that badge
- CThe total elapsed time figure at the top of the profile, which by itself tells the developer which join operator dominated the query runtime
- DThe percentage of execution time shown on each operator node, which ranks the nodes so the costliest operator can be identified and tuned first Correct
Why A is wrong: The query id is an opaque identifier and does not encode operator cost, so it cannot reveal which step in the plan is the most expensive.
Why B is wrong: The profile shows warehouse details but no per-operator size badge that flags the slowest step, so this is not how the expensive operator is found.
Why C is wrong: Total elapsed time gives the whole query duration only and does not attribute cost to any single operator, so it cannot isolate the most expensive step.
Why D is correct: Each operator node in Query Profile reports its share of total execution time, so reading the highest percentage points the developer straight to the costliest step to tune.