Snowflake — Module 14

Cost Optimization

Credits, warehouses, auto-suspend, query waste, resource monitors, chargeback, budgets, and query history.

75 min September 2026

Performance Tuning Advanced Security and Governance

// Part 01 — Plain-English foundation

Cost Optimization From Scratch

Snowflake cost is mostly credits for compute plus storage and cloud services. Cost optimization means aligning warehouse runtime and size with actual business value.

Why this matters: Snowflake can become expensive quietly. Warehouses left running, oversized transformations, dashboard refresh storms, and duplicate pipelines can burn thousands before anyone notices.

Mental model

Credits are electricity. Warehouses are machines. Auto-suspend turns machines off, warehouse size controls how much electricity they use while running, and query design decides how long the machines work.

// Part 02 — Core concepts

The Concepts You Must Own

✓Virtual warehouses consume credits while running.
✓Auto-suspend and auto-resume are first-line cost controls.
✓Resource monitors can alert or suspend when credit thresholds are hit.
✓Query history and warehouse metering reveal cost drivers.
✓Chargeback/showback creates accountability by team or workload.

Concept	Meaning	Why it matters
Credits	Compute billing unit.	Primary cost driver for active warehouses.
Auto-suspend	Stops inactive compute.	Prevents idle spend.
Resource monitor	Quota/alert control.	Guardrail against runaway spend.
Warehouse history	Usage over time.	Identifies expensive workloads.
Query attribution	Who/what ran expensive SQL.	Turns cost into accountability.

// Part 03 — How the work actually flows

Step-by-Step Workflow

✓Inventory warehouses, owners, sizes, and auto-suspend settings.
✓Review warehouse metering history for top credit consumers.
✓Find long-running, repeated, and queued queries.
✓Right-size warehouses and split noisy workloads.
✓Add resource monitors, budgets, tags, and review cadence.

Cost Optimization example

CREATE RESOURCE MONITOR BI_MONITOR
  WITH CREDIT_QUOTA = 500
  FREQUENCY = MONTHLY
  START_TIMESTAMP = IMMEDIATELY
  TRIGGERS
    ON 75 PERCENT DO NOTIFY
    ON 95 PERCENT DO SUSPEND;

ALTER WAREHOUSE WH_BI_S SET
  AUTO_SUSPEND = 60
  AUTO_RESUME = TRUE;

SELECT warehouse_name, SUM(credits_used) AS credits
FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY
WHERE start_time >= DATEADD(day, -30, CURRENT_TIMESTAMP())
GROUP BY 1
ORDER BY credits DESC;

Do not read the example as magic syntax to memorize. Read it as a production habit: name the objects clearly, make assumptions visible, preserve enough metadata to debug later, and keep the business promise attached to the SQL.

// Part 04 — Mistakes and debugging

Common Mistakes That Break Snowflake Projects

Watch these carefully

✓Setting auto-suspend to hours for ad hoc warehouses.
✓Running every workload on a large warehouse because it “feels safer.”
✓Ignoring BI tools that refresh many dashboards automatically.
✓Optimizing storage pennies while compute dollars burn.
✓Having no owner for shared warehouses.

How to debug this topic

Start by asking what promise failed: freshness, correctness, access, speed, or cost. Then inspect the Snowflake evidence: query history, warehouse metering, task history, copy history, grants, row counts, and sample records. Good Snowflake debugging is not guessing. It is reading the platform metadata until the failure has a shape.

// Part 05 — Production depth

Production Notes

✓Tag warehouses by team, environment, and purpose.
✓Use separate warehouses for load, transform, BI, and experiments when it improves accountability.
✓Create weekly cost review reports from ACCOUNT_USAGE.
✓Budget in workload terms: dashboard freshness, pipeline SLA, and analyst concurrency.

Production standard: A Snowflake design is not complete when the query returns rows. It is complete when the team knows who owns it, how fresh it should be, how access is controlled, what it costs, how to detect failure, and how to recover safely.

// Part 06 — Interview and project readiness

Explain It Like a Professional

Cost optimization starts with warehouse runtime, size, auto-suspend, query efficiency, and workload isolation. Mention resource monitors, metering history, query history, tags, and showback. Good answers tie cost to SLA: spend where freshness and performance matter, reduce waste elsewhere.

Mini project

Build a Snowflake cost dashboard showing credits by warehouse, top users, longest queries, idle warehouses, and resource monitor alerts. Propose three savings actions and expected tradeoffs.

Questions you should answer out loud

✓How would you explain Cost Optimization to a non-technical manager?
✓Which Snowflake objects, roles, or SQL statements does this topic use?
✓What can fail in production and which metadata view would you inspect first?
✓What is the cost or security risk if this is implemented carelessly?
✓How would you test that the result is correct and rerunnable?

🎯 Key Takeaways

✓Compute credits dominate many Snowflake bills.
✓Auto-suspend is a basic but powerful control.
✓Cost needs owners and visibility.
✓Resource monitors provide guardrails.
✓Optimize cost against business SLA, not just lower numbers.

Performance Tuning

Advanced Security and Governance

Discussion

Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.

Continue with GitHub