Skip to content
Finitizer
To investigate

Snowflake background services: credits outside warehouses

Some Snowflake features bill credits without a warehouse of yours running, such as automatic clustering, Snowpipe and materialized view upkeep.

They appear on the bill as their own service types.

Run this check on your own account

Run read-only queries in your own console and paste the results. The report is worked out in your browser, with no access to your account.

What the check looks at

Credits by service type from METERING_DAILY_HISTORY, for every service that is not a warehouse or cloud services.

Why it costs money

  • Automatic clustering, materialized view maintenance, search optimization, Snowpipe, serverless tasks, replication and Query Acceleration each bill credits for work Snowflake does on its own compute.
  • They run when data changes, so a table that is rewritten often can keep them busy every day.
  • Because no warehouse of yours is running, they are easy to miss when you look only at warehouse costs.

How the tool measures it

To investigate. The report shows what this costs now and where to look. It claims no saving, because the results cannot prove one.

The report lists each service type's credits and share of the bill from query 1, at your credit price. It claims no saving.

When the report raises it. Query 1 shows credits for any service other than warehouses and cloud services.

In the sample report

Background services

From the tool's own sample: made-up results for one account over 30 days, priced at Enterprise list prices in US East (N. Virginia).

What to do

  1. 1Rank the service types by credits in the report.
  2. 2For automatic clustering and materialized views, check how often the underlying tables change and whether the clustering key or view is still used.
  3. 3For Snowpipe, check whether many small files could be batched.

How to tell it worked. Compare that service type's daily credits in METERING_DAILY_HISTORY for two weeks before and after a change.

Trade-offs. These services make queries faster or data fresher. Turning one off can cost more in warehouse time than it saves.

The read-only query behind it

The same SQL the tool gives you. Each reads usage views and changes nothing.

Query 1: credits by service and average storage
-- Finitizer Snowflake Cost Check, query 1 of 5: the account bill
-- sf-cost-check-v1 (2026-11-10). Read-only: it reads Account Usage and changes nothing.
-- Credits by service for the last 30 complete UTC days, and average storage. Totals only.
-- Needs ACCOUNTADMIN, or a role with IMPORTED PRIVILEGES on the SNOWFLAKE database.
WITH w AS (
  SELECT DATEADD(day, -30, DATE_TRUNC('day', CONVERT_TIMEZONE('UTC', CURRENT_TIMESTAMP()))) AS ws,
         DATE_TRUNC('day', CONVERT_TIMEZONE('UTC', CURRENT_TIMESTAMP())) AS we
),
s AS (
  SELECT COUNT(*) AS days,
         AVG(storage_bytes) AS database_bytes,
         AVG(stage_bytes) AS stage_bytes,
         AVG(failsafe_bytes) AS failsafe_bytes,
         AVG(hybrid_table_storage_bytes) AS hybrid_bytes
  FROM snowflake.account_usage.storage_usage, w
  WHERE usage_date >= w.ws::DATE AND usage_date < w.we::DATE
)
SELECT 'credits' AS row_kind,
       m.service_type AS item,
       SUM(m.credits_used_compute)::FLOAT AS credits_compute,
       SUM(m.credits_used_cloud_services)::FLOAT AS credits_cloud_services,
       SUM(m.credits_adjustment_cloud_services)::FLOAT AS credits_adjustment,
       SUM(m.credits_billed)::FLOAT AS credits_billed,
       COUNT(DISTINCT m.usage_date) AS days,
       NULL::FLOAT AS average_bytes,
       TO_VARCHAR(MIN(w.ws), 'YYYY-MM-DD') AS window_start,
       TO_VARCHAR(MIN(w.we), 'YYYY-MM-DD') AS window_end,
       CURRENT_REGION() AS region
FROM snowflake.account_usage.metering_daily_history m, w
WHERE m.usage_date >= w.ws::DATE AND m.usage_date < w.we::DATE
GROUP BY m.service_type
UNION ALL
SELECT 'storage', 'database', NULL, NULL, NULL, NULL, s.days, s.database_bytes::FLOAT,
       TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'stage', NULL, NULL, NULL, NULL, s.days, s.stage_bytes::FLOAT,
       TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'failsafe', NULL, NULL, NULL, NULL, s.days, s.failsafe_bytes::FLOAT,
       TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
UNION ALL
SELECT 'storage', 'hybrid', NULL, NULL, NULL, NULL, s.days, s.hybrid_bytes::FLOAT,
       TO_VARCHAR(w.ws, 'YYYY-MM-DD'), TO_VARCHAR(w.we, 'YYYY-MM-DD'), CURRENT_REGION()
FROM s, w
ORDER BY row_kind, credits_billed DESC NULLS LAST;

Other checks in the report

All checks

What a credit and a terabyte cost in each region and edition: Snowflake pricing in 2026. Finitizer does this for BigQuery today. Snowflake and Redshift support is on the way.