QuestionQ105

Performance Optimization, Querying & Transformation

Which field in the ACCOUNT_USAGE.QUERY_HISTORY view indicates the amount of time a query spends waiting for resources because of concurrency (i.e., too many queries competing for the same warehouse resources)?

Explanation

QUEUED_OVERLOAD_TIME is the QUERY_HISTORY column that records the time (in milliseconds) a query spends in the warehouse queue because the warehouse is overloaded by the current concurrent query workload — that is, other queries are consuming the available compute resources. By contrast, QUEUED_PROVISIONING_TIME measures wait time due to warehouse compute resources being provisioned (creation, resume, or resize), QUEUED_REPAIR_TIME measures wait time due to compute resources needing repair, and TRANSACTION_BLOCKED_TIME measures time blocked by a concurrent DML transaction (locking), none of which specifically represent concurrency-driven contention for warehouse compute capacity.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!