An Architect is investigating a long-running statement and must identify the transactions that are blocked and the queries blocking them.
Which views should be used for troubleshooting?
LOCK_WAIT_HISTORY contains the history of transactions waiting for locks and exposes the blocking queries. QUERY_HISTORY provides the SQL statement and transaction details needed to investigate both the blocked and blocking activity. Snowflake’s documented workflow for examining a long-running statement uses these two Account Usage views together.
Community Discussion