A Snowflake Administrator is investigating why a query is not re-using the persisted result cache. The Administrator found the two relevant queries from the SNOWFLAKE. ACCOUNT_USAGE. QUERY_HISTORY…

Question

Options

• AThe second query includes a CURRENT_TIMESTAMP () function.
• BThe second query includes a CURRENT_DATE () function.
• CThe queries are executed with two different virtual warehouses.
• DThe queries are executed with two different roles.

• A
  69% (25)
• B
  6% (2)
• C
  14% (5)
• D
  11% (4)

Explanation

The inclusion of the CURRENT_TIMESTAMP() function in the second query prevents it from re- using the first query's persisted result cache because this function makes each execution unique due to the constantly changing timestamp. According to the Snowflake documentation, "The query does not include non-reusable functions, which return different results for successive runs of the same query. UUID_STRING, RANDOM, and RANDSTR are good examples of non- reusable functions." The CURRENT_TIMESTAMP() function is another example of a non- reusable function, as it returns the current date and time at the start of query execution, which varies for each run. Therefore, the second query is not identical to the first query, and the result cache is not reused.

No community discussion yet for this question.