Understanding Credit Consumption

Snowflake · Cost Management & Monitoring

Theory

Most Snowflake usage is measured in credits, a unit priced according to your contract and edition. Virtual warehouses consume credits per second while running, based on size. Serverless features such as Snowpipe, automatic clustering, materialized view maintenance, search optimization, serverless tasks and Cortex functions also consume credits. Cloud services usage consumes credits too, but it is billed only for the part that exceeds 10% of that day's warehouse usage.

Storage is billed separately, as a monthly charge on the average compressed data stored, including Time Travel and Fail-safe data. Moving data out to other regions or clouds can add data transfer charges. ACCOUNT_USAGE views such as WAREHOUSE_METERING_HISTORY show where credits went.

Why we use it

Without knowing what consumes credits, bills grow from idle warehouses, oversized compute or forgotten serverless features. Knowing the cost drivers lets you control spend without hurting performance.

When to use it

Review credit usage regularly, especially after adding warehouses or enabling serverless features. Use warehouse metering views for compute, METERING_DAILY_HISTORY for all services, and storage views for growth in table, Time Travel and Fail-safe bytes.

Compute Credits

Every running virtual warehouse burns credits per second (after an initial minimum), scaled by its T-shirt size — an X-Small burns roughly 1 credit/hour, a Small 2, doubling up the size ladder.

Storage Costs

Billed separately from compute, purely on compressed data volume per month, at a flat per-terabyte rate that doesn't change with how often the data is queried.

Serverless Feature Costs

Features like Snowpipe, automatic clustering, and Search Optimization run on Snowflake-managed compute outside any warehouse you control, and are billed as their own line item.

How it works

  1. Bill or usage looks high
  2. Query METERING_DAILY_HISTORY by service type
  3. Is warehouse compute the main cost? Yes: Check WAREHOUSE_METERING_HISTORY: idle time, size, auto-suspend. No: Check serverless features or storage.
  4. Fix the cause: suspend, resize, drop unused features or data
  5. Add resource monitors and budgets to keep it in check

Example

SELECT WAREHOUSE_NAME, SUM(CREDITS_USED) AS total_credits
FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY
WHERE START_TIME >= DATEADD(MONTH,-1,CURRENT_TIMESTAMP())
GROUP BY WAREHOUSE_NAME ORDER BY total_credits DESC;

Key points

Snowflake topics

Snowflake Fundamentals

Warehouses & Performance

Staging & SnowSQL

Tables & Data Handling

Cloud Integrations

Storage & Optimization

Security & Governance

Views, Pipelines & Automation

Data Types & SQL Fundamentals

Semi-Structured Data Deep Dive

Advanced Features

Data Sharing & Collaboration

Cost Management & Monitoring

Databases, Schemas & Objects

Performance Deep Dive

Advanced Security & Governance

Stored Procedures & UDFs

Ecosystem & Integrations

SnowPro Certification Prep

T
Tech Town
Log InSign Up Free
Home SQL Python DSA Power BI Snowflake Databricks Spark Gen AI Practice Problems Contest Blog

Mastering Snowflake

The modern data cloud, from architecture to SnowPro certification. Click any topic in the sidebar to open it right here.

{{ sectionCount }}
Sections
{{ topicCount }}
Topics
Free
Forever
Hands-on practice Practice Snowflake SQL Sharpen the SQL you use in Snowflake: 150 query problems in a live editor with instant checking. Start practising →
Section {{ sec.num }}

{{ sec.label }}

Snowflake  /  {{ current.sectionLabel }}  /  {{ current.name }}

{{ current.name }}

Theory

{{ current.def }}

Why we use it

{{ rich.why }}

When to use it

{{ rich.when }}

{{ sec.h }}

{{ sec.body }}

{{ sec.body }}

Diagram

{{ rich.dg.caption }}

{{ tb.title }}
{{ c.v }}
{{ rich.dg.op }}
➜
{{ rich.dg.output.title }}
{{ c.v }}
{{ nd.label }}
{{ nd.sub }}
{{ nd.label }}
{{ nd.sub }}
{{ rich.dg.left.title }}
{{ it }}
{{ rich.dg.right.title }}
{{ it }}
On screen — where to click

{{ rich.ui.title }}

{{ u.text }}
  1. {{ st.n }}{{ st.text }}
{{ rich.ui.title }}
{{ u.text }}
Flowchart — how it works
{{ nd.text }}
{{ nd.text }}
◇ {{ nd.text }}
Yes → {{ nd.yes }}
No → {{ nd.no }}
Syntax
{{ current.syntax }}
Example
{{ current.example }}
Want to run this yourself? Unlike the SQL and Python courses, Snowflake needs a real account — there's no in-browser engine for it. Click Copy above, then paste it into a free Snowflake trial (30 days, no card required) and run it in Snowsight.
Key Points — click to check off as you learn
  • {{ pt.mark }} {{ pt.text }}

Share this topic