What actions will prevent leveraging of the ResultSet cache? (Choose two.)
What actions will prevent leveraging of the ResultSet cache? (Choose two.)
Removing a column from the query SELECT list will change the structure of the query, resulting in not being able to use the cached ResultSet. Changing a column that is not in the cached query can still impact the cached result, as updates to the table schema or data can invalidate the cached results.
C is explained here "The table’s micro-partitions have not changed (e.g. been reclustered or consolidated) due to changes to other data in the table." https://docs.snowflake.com/en/user-guide/querying-persisted-results.html
ACE are correct.
Clustering will not prevent use of cached results, reclustering or consolidation will.
A, C and E is correct. I tried all and the cache was not used
E. Changing a column that is not in the cached query >> bypass RESULT CACHE (TABLE SCAN - Percentage scanned from cache 100.00%). Hitting RESULT CACHE = QUERY RESULT REUSE (Node Execution Time (0ms) 100.0%)
AE are correct
ACE are correct. I've checked the case of E, and persisted query cache was not retrieved
I checked the last one. it doesn't leverage result set cache
Why not B ?
B says when VW is suspended ,but query result cache does not interact with VW while quering so it has no impact
If "Changing a column that is not in the cached query" means changing such column's name or updating the data of that column then ACE are correct answers.
A and C are correct
I think it's not REclustering so C is not correct
By clustering you are reorganizing the micro partitions thereby preventing resultset cache to reuse.. So A and C ae correct
A -- Correct E -- Correct Tested with update on column that is not part of the cached query, after that cached cannot be used.
AC is correct
Should be A, B
Correct
AC correct option
AC correct option