Slow or Long-Running Query Performance: Troubleshooting Checklist
A common cause of slow queries is that the joins produce more rows than the query author anticipated. This is referred to as “row explosion.” An easy way to recognize these is to check the query profile for join operators that display…
How to diagnose a slow running query
If the Status column displays a status of Queued for the query, the cause of the slowness is most likely due to insufficient compute resources. If the running query load is high or there’s queuing, consider starting a separate…
Understanding why compilation time in Snowflake can be higher than execution time
The more complex the query, the longer it takes for the optimizer to create the query plan. As a result, the compilation time can be longer than the execution time. Tables: The number of tables and columns in the query also affects the…
Working with Materialized Views
Query results contain results that require significant processing, including: Analysis of semi - structured data. Aggregates that take a long time to calculate. The query is on an external table, which might have slower performance compared…
Monitor query activity with Query History
If a Load More button appears at the top of the list, it means that there are more available results to load. You can fetch the next set of results by either selecting Load More or scrolling to the bottom of the list.
Optimizing storage for performance
Among these micro - partitions, Snowflake organizes (i.e. clusters) data based on dimensions of the data. If a query filters, joins, or aggregates along those dimensions, fewer micro - partitions must be scanned to return results, which speeds…
The connection.destroy function in the NodeJS driver takes few minutes to cancel a query.
This lag is due to Snowflake’s internal process for managing sessions and ensuring that all resources are properly cleaned up before the session is completely closed.
Using Persisted Query Results
For persisted query results of all sizes, the cache expires after 24 hours. Note that the security token used to access large persisted query results (i.e. greater than 100 KB in size) expires after 6 hours. A new token can be retrieved to…
After enabling the ENABLE_INTERNAL_STAGES_PRIVATELINK parameter, the GET_PRIVATELINK_CONFIG function takes several minutes to execute
CAUSE: This slowness is introduced by an Azure - known performance issue. SOLUTION: Open a support case with Snowflake Support, and provide the value of the privatelink - internal - stage parameter found in the output of the…
Analysing Long running Metadata Operations
They access specialized metadata services of a snowflake, metadata operations are not dependent on warehouse or customer data storage. They are serial operations, but a single customer query can have the flavor of both metadata operation…
Source