Our SQL query costs doubled overnight on Snowflake due to an unoptimized join in our BI layer, so how do I find and kill that specific query right now?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Our SQL query costs doubled overnight on Snowflake due to an unoptimized join in our BI layer, so how do I find and kill that specific query right now?
1 real search · 1 real-search pass
site:docs.snowflake.com SYSTEM$CANCEL_QUERY QUERY_HISTORY Information Schema query history running query cancellationGoogle ↗
OBSERVED
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 1 queries…
Searches and sources
ChatGPT1 real searches · gpt-6
site:docs.snowflake.com SYSTEM$CANCEL_QUERY QUERY_HISTORY Information Schema query history running query cancellation Google ↗
- SYSTEM$CANCEL_QUERY · docs.snowflake.com
- Canceling Statements · docs.snowflake.com
- QUERY_HISTORY view · docs.snowflake.com
- Monitor query activity with Query History · docs.snowflake.com
- Exploring execution times · docs.snowflake.com