One of your colleagues has submitted a long running query in Snowflake. how long the query can run till snowflake automatically cancels the query?

One of your colleagues has submitted a long running query in Snowflake. how long the query can run till snowflake automatically cancels the query?
A . 14 hours
B. 2 days
C. 2 hours
D. 24 hours

View Answer

Answer: B

Explanation:

This is actually a dangerous thing to happen in production, hence it is recommended to setup mechanism to monitor long running jobs and kill them if they are running beyond a threshold. https://docs.snowflake.com/en/sql-reference/parameters.html#statement-timeout-in-seconds STATEMENT_TIMEOUT_IN_SECONDS

Type

Session and Object (for warehouses)

Can be set for Account » User » Session; can also be set for individual warehouses

Data Type

Number

Description

Amount of time, in seconds, after which a running SQL statement (query, DDL, DML, etc.) is canceled by the system.

The parameter can be set within the session hierarchy. It can also be set for an individual warehouse to control the runtime for all SQL statements processed by the warehouse. When the parameter is set for both a warehouse and a session, the lowest non-zero value is enforced. For example: A warehouse has a timeout of 1000 seconds.

The timeout for the session is set to 500 seconds.

The session timeout takes precedence (i.e. any statement submitted in the session is canceled after

running for longer than 500 seconds).

Values

0 to 604800 (i.e. 7 days) ― a value of 0 specifies that the maximum timeout value is enforced. Default

172800 (i.e. 2 days)