Home / Snowflake / Cost optimization
Snowflake cost optimization
Snowflake cost optimization: find where your credits go, then cut the waste
Snowflake bills compute by the second while a warehouse runs, and each size step doubles the rate. Small settings add up. For data and platform teams with a growing Snowflake bill: we review your ACCOUNT_USAGE data, right-size warehouses, tune auto-suspend and the queries that burn the most credits, and set resource monitors and budgets so costs stay down. Prefer to do it yourself? Start with our guide to reducing Snowflake costs.
Quick answer
How do you reduce Snowflake costs?
Most Snowflake savings come from right-sizing virtual warehouses, shortening auto-suspend timers, fixing inefficient queries that scan too much data, reviewing automatic clustering and other serverless features, trimming storage retention, and adding resource monitors. Each warehouse size step doubles the credit rate, from 1 credit per hour for X-Small to 64 for 3X-Large, so oversized warehouses are the most common cause of overspend.
Why size matters
Each warehouse size doubles the credit rate
Credits per hour for standard virtual warehouses. A warehouse sized one step too large for its workload costs twice as much for every hour it runs.
Billing is per second with a 60-second minimum each time a warehouse resumes, so auto-suspend settings and query patterns matter as much as size.
| Size | Credits / hour | Relative |
|---|---|---|
| X-Small | 1 | |
| Small | 2 | |
| Medium | 4 | |
| Large | 8 | |
| X-Large | 16 | |
| 2X-Large | 32 | |
| 3X-Large | 64 |
What we review
Where savings usually come from
Warehouse sizing
Match size to workload using query history. Split mixed workloads so a heavy job doesn't set the size for everything.
Auto-suspend and idle time
Tune suspend timers, and find warehouses that are kept awake by BI tool polling or chatty schedulers.
Query tuning
Fix full-table scans, poor pruning, exploding joins and repeated work that caching or incremental models would avoid.
Clustering and serverless features
Check that automatic clustering, materialized views, search optimization and Snowpipe are earning their cost.
Storage
Review Time Travel retention, transient tables for staging data, and unused tables and clones.
Guardrails
Resource monitors, budgets and statement timeouts, plus a cost dashboard by team or workload.
Process
How a cost review runs
Read-only access
We work from the ACCOUNT_USAGE views such as WAREHOUSE_METERING_HISTORY and QUERY_HISTORY. No access to your business data is needed for the analysis.
Findings
A ranked list of cost drivers, each with the estimated saving, the fix and the risk of making it.
Fixes
We make the changes you approve, or hand them to your team with exact steps.
Guardrails
Monitors, alerts and a cost dashboard so spend stays visible after we finish.
The bill
Where Snowflake credits and costs go
| Cost line | How it is billed | Common waste |
|---|---|---|
| Virtual warehouses | Credits per second while running, 60-second minimum per resume | Oversized warehouses, long auto-suspend, BI tools keeping warehouses awake |
| Serverless features | Credits for Snowpipe, automatic clustering, materialized views, search optimization, serverless tasks and replication | Clustering or search optimization on tables that don't need it |
| Cloud services | Billed only above 10% of daily warehouse usage | Very frequent tiny queries, heavy metadata operations |
| Storage | Per terabyte per month, including Time Travel and Fail-safe | Long Time Travel on staging tables, forgotten clones and backups |
| Data transfer | Egress across regions or clouds | Cross-region replication or unloads nobody uses |
Start here
Find your most expensive warehouses
This query, run with access to the SNOWFLAKE database, lists credits by warehouse for the last 30 days. It is usually the first thing we run in a cost review.
SELECT warehouse_name,
ROUND(SUM(credits_used), 1) AS credits_30d
FROM snowflake.account_usage.warehouse_metering_history
WHERE start_time >= DATEADD(day, -30, CURRENT_TIMESTAMP())
GROUP BY warehouse_name
ORDER BY credits_30d DESC;Quick wins checklist
- Auto-suspend set to about 60 seconds on loading and transformation warehouses
- Separate warehouses for loading, transformation and BI
- Statement timeouts so runaway queries stop
- Resource monitors with notify and suspend thresholds
- Transient tables for staging data, with short Time Travel
- Unused tables, clones and stages removed
- Clustering and search optimization checked against their benefit
Deliverables
What you get from a Snowflake cost review
A short report, not a tool export: the cost drivers ranked by estimated saving, the exact change for each, its effect on performance, and who should make it. Changes you approve are applied and measured, so you see the before and after in the same usage views Snowflake bills from.
Want cost to stay down after the review? Our Snowflake engineers can keep watch as part of your team, and the database optimization guide explains the query side.
Report contents
- Spend by warehouse, feature and team
- Top 20 queries by credit cost
- Ranked fixes with estimated savings
- Guardrail settings to apply
- Before and after measurements
Contact us
Ask for a Snowflake cost review
Tell us roughly what you spend on Snowflake each month and what has grown. We'll reply with where we'd look first.
- A senior engineer reads every message
- Reply within one business day
- No obligation, and your details are used only to reply
Prefer the full form? Go to the contact page.
FAQ
Questions buyers ask us
What access do you need for a cost review?
A role with read access to the SNOWFLAKE.ACCOUNT_USAGE views. We do not need access to your business data for the analysis.
Will changes affect query performance?
Each finding lists its performance risk. We test changes on a non-production warehouse or during a low-traffic window first.
How much can a Snowflake cost review save?
It depends on how the account is run. Oversized warehouses, long auto-suspend timers and a few expensive queries are the most common drivers, and fixing them usually brings the largest savings. Each finding in our review comes with an estimate before you approve it.
Does Snowflake charge when a warehouse is idle?
Not when it is suspended. A running warehouse is billed per second even with no queries, which is why auto-suspend settings matter. Each resume has a 60-second minimum charge.
What are Snowflake cloud services charges?
Cloud services cover work such as query compilation and metadata. Snowflake bills them only for the part that exceeds 10% of that day's warehouse usage, so most accounts pay little or nothing for them.
Next step
Tell us what you need to build or who you need to hire.
A 30-minute call with a senior architect. You leave with a scoped plan or a role profile, whether or not you work with us.