Schema:: ACCOUNT_USAGE

QUERY_INSIGHTS view¶

This Account Usage view displays a row for each insight produced for a query.

Columns¶

Column name	Type	Description
`start_time`	TIMESTAMP_LTZ	Start time of the query.
`end_time`	TIMESTAMP_LTZ	End time of the query.
`total_elapsed_time`	NUMBER	Total elapsed time of the query (in milliseconds).
`query_id`	VARCHAR	Internal/system-generated identifier for the SQL statement.
`query_hash`	VARCHAR	The hash value computed based on the canonicalized SQL text.
`query_parameterized_hash`	VARCHAR	The hash value computed based on the parameterized query.
`warehouse_id`	VARCHAR	Internal/system-generated identifier for the warehouse that was used.
`warehouse_name`	VARCHAR	Warehouse that the query executed on, if any.
`insight_instance_id`	NUMBER	Internal/system-generated identifier for the insight.
`insight_type_id`	VARCHAR	Identifier of the insight type.
`message`	VARIANT	Structured information and details about the insight.
`suggestions`	ARRAY	Array of strings, each containing a recommended action for the insight.
`is_opportunity`	BOOLEAN	If `true`, the insight includes suggestions to improve query performance. For example: For an insight with the type ID `QUERY_INSIGHT_FILTER_WITH_CLUSTERING_KEY`, this column contains `false` because the insight does not include suggestions for improving performance.
`insight_topic`	VARCHAR	Label that identifies the type of performance impact detected by this insight. The label can be one of the following: `TABLE_SCAN`: Insights about the efficiency of accessing tables. This label applies to the following types of insights: `QUERY_INSIGHT_INAPPLICABLE_FILTER_ON_TABLE_SCAN` `QUERY_INSIGHT_UNSELECTIVE_FILTER` `QUERY_INSIGHT_FILTER_WITH_CLUSTERING_KEY` `JOIN`: Insights about the efficiency of JOIN operations in the query. This label applies to the following types of insights: `QUERY_INSIGHT_JOIN_WITH_NO_JOIN_CONDITION` `WAREHOUSE`: Insights about the warehouse used for the query. This label applies to the following types of insights: `QUERY_INSIGHT_REMOTE_SPILLAGE`

Usage notes¶

Latency for the view may be up to 90 minutes.

Examples¶

The following example returns the query insights for the query with the ID 01bd3a9d-0910-8327-0000-09717704c032:

SELECT query_id, insight_type_id, message, suggestions
  FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_INSIGHTS
  WHERE query_id = '01bd3a9d-0910-8327-0000-09717704c032';

Copy

The following example returns the query insights for queries that have the same hash of parameterized query text. These are queries that use the same SELECT statement except for the literals specified in the statement.

SELECT query_id, insight_type_id, message, suggestions
  FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_INSIGHTS
  WHERE query_parameterized_hash = '4bb66effc1a3c8b4e94a728f7caaa736';

Copy

The following example returns the query insights for queries that ran during the past week:

SELECT query_id, insight_type_id, message, suggestions
  FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_INSIGHTS
  WHERE start_time > TO_DATE(DATEADD(DAY, -7, CURRENT_DATE()));

Copy

The following example returns the query insights for queries that ran during the past week and took more than an hour to complete:

SELECT query_id, insight_type_id, message, suggestions
  FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_INSIGHTS
  WHERE start_time > TO_DATE(DATEADD(DAY, -7, CURRENT_DATE()))
    AND total_duration > 3600000;

Copy

The following example returns the query insights for queries that ran during the past week, took more than an hour to complete, and used the warehouse with the ID 84412315:

SELECT query_id, insight_type_id, message, suggestions
  FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_INSIGHTS
  WHERE start_time > TO_DATE(DATEADD(DAY, -7, CURRENT_DATE()))
    AND total_duration > 3600000
    AND warehouse_id = 84412315;

Copy