Recall the first signals to inspect in Snowflake Query Profile.
First read What should you separate before proposing a fix? Queue time versus execution work. Queueing points to concurrency or warehouse availability; execution points to SQL shape, scan, spill, or compute capacity. Symptom Bytes scanned or rows returned? A query can return 100 rows after scanning billions. Objection The query only returns one row, so Snowflake must be broken. The result is a single metric tile. Your line The output is small, but the profile tells us how much data was scanned to produce it. Let us check bytes scanned and pruning before resizing. Judging cost by output size ignores…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in