Snowflake Warehouse Oversized
Each successive warehouse size generally doubles the credits consumed per hour, so a warehouse larger than the query needs can cost more than the shorter runtime saves.
Free to start. No card. The playground just needs your work email.
Snowflake
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Snowflake, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce the warehouse size. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Snowflake Warehouse on Snowflake
- The fix, by hand
- Open Snowsight → Admin → Warehouses → the resource and review the size + WAREHOUSE_LOAD_HISTORY heatmap.
- Confirm p95 load is well below 100% and there is no significant queueing or remote spillage.
- Drop one size step (e.g., LARGE → MEDIUM): ALTER WAREHOUSE the resource SET WAREHOUSE_SIZE = '‹next_smaller›';.
- Watch QUERY_HISTORY for new queueing or remote-spill bytes over the next 7 days.
- Right-size before adding multi-cluster scaling. Each size step halves credits/hour.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-2104- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.