Why is trying to diagnose a failed SQL statement from the storage bill an unsound approach?
Select an answer to reveal the explanation.
Short Explanation
A bill tells you how much, never which statement or why it failed. The error text and execution record are sitting in query history, which is where the diagnosis actually starts.
Full Explanation
The correct answer is the statement that billing reports aggregate cost and cannot identify the statement, its error, or its execution details, all of which query history records. Cost reporting is aggregated by resource and period. It has no notion of an individual statement, no error text, and no execution plan, so it cannot answer why a query failed. The claim that storage bills are only issued monthly, so delay is the problem, is incorrect because timeliness is a secondary complaint; even a real-time bill would carry none of the diagnostic detail. The claim that failed queries are excluded from billing, so they never appear, is incorrect because whether a failed query is billed is irrelevant to its diagnosis. The claim that billing data is stored in a format that engines cannot read is incorrect because readability of billing data is not the obstacle; the data simply does not contain what is needed. For the exam, diagnose failures from the error and the execution record in query history.