I have a QlikSense application( may 2024 version) sourced from Snowflake. For the past year, my extract query has been running successfully in production, with daily data loads completing without issues. However, today, an error occurred—the query took more than two hours and failed with a “warehouse timed out” error (Error Code: 630).
Our database administrator says that a query runs for more than 2 hours and fails due to the unmasked role of one table in the snowflake SQL query. Snowflake's query plan generation is dynamic and sometimes generates bad plans. Only specific queries are impacted, while others work fine. Is that true? Do you have any resolution?
In Snowflake, the query owner or developer has no direct control over how the query executes once it is submitted. Is that true? Snowflake’s cost-based optimizer (CBO) dynamically decides the execution plan .? My snowflake query was running successfully in 10 minutes since the last one year. All of the sudden yesterday it was taking long run time and timeout? Can you confirm developer is not having any control over snowflake SQL query?Qliksense having any solutions in script level? Qliksense+ Snowflake backend sometimes extract query execution time takes longer because of cost based optimizer ? Any resolution from Qliksense?
