Running EXPLAIN on a query does not require a running warehouse

Running EXPLAIN on a query does not require a running warehouse
A . TRUE
B. FALSE

View Answer

Answer: A

Explanation:

EXPLAIN compiles the SQL statement, but does not execute it, so EXPLAIN does not require a running

warehouse.

Although EXPLAIN does not consume any compute credits, the compilation of the query does consume

Cloud Service credits, just as other metadata operations do.

To post-process the output of this command, you can:

Use the RESULT_SCAN function, which treats the output as a table that can be queried.

Generate the output in JSON format and insert the JSON-formatted output into a table for analysis later. If you store the output in JSON format, you can use the function SYSTEM$EXPLAIN_JSON_TO_TEXT or EXPLAIN_JSON to convert the JSON to a more human readable format (either tabular or formatted text).

The assignedPartitions and assignedBytes values are upper bound estimates for query execution. Runtime optimizations such as join pruning can reduce the number of partitions and bytes scanned during query execution.

The EXPLAIN plan is the "logical" explain plan. It shows the operations that will be performed, and their logical relationship to each other. The actual execution order of the operations in the plan does not necessarily match the logical order shown by the plan. https://docs.snowflake.com/en/sql-reference/sql/explain.html#usage-notes