Skip to content
Finitizer
Priced

Snowflake transient tables: cutting Fail-safe storage

Permanent Snowflake tables keep 7 days of Fail-safe after their Time Travel ends, and that history bills as storage.

Tables you can rebuild from their source, like staging and scratch tables, can be transient and keep none.

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

Storage by database from TABLE_STORAGE_METRICS: active bytes, Time Travel bytes and Fail-safe bytes, and the permanent tables whose Time Travel and Fail-safe outweigh their own data.

Why it costs money

  • Every change to a permanent table keeps the old micro-partitions for the Time Travel period (1 day by default, up to 90 on Enterprise) and then 7 more days of Fail-safe.
  • Tables that are truncated and reloaded every day build up history much larger than the table itself.
  • Transient tables have no Fail-safe and at most 1 day of Time Travel, so their history stays small.

How the tool measures it

Priced. The report puts a monthly saving range on this check, from your own query results at your price.

For tables whose Time Travel and Fail-safe bytes are larger than their active bytes, the high end is their Time Travel and Fail-safe bytes and the low end is their Fail-safe bytes alone, at your storage price per TB a month.

When the report raises it. Query 4 is provided and some tables' history outweighs their data.

In the sample report

Transient table candidates

  • RAW: 6 tables.
  • STAGING: 9 tables.

$143 to $260 a month, modeled.

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. 1Run the follow-up query on the tool page for the database, to list the tables.
  2. 2Keep only the tables that are rebuilt from a source you still have.
  3. 3Recreate each one as transient (CREATE TRANSIENT TABLE ... AS SELECT, or clone into a transient schema), or lower its DATA_RETENTION_TIME_IN_DAYS.

How to tell it worked. A week after the change, read TIME_TRAVEL_BYTES and FAILSAFE_BYTES for those tables in TABLE_STORAGE_METRICS. The old Fail-safe bytes drop off over its 7 days.

Trade-offs. Snowflake cannot recover a transient table from Fail-safe. Only use it for data you can rebuild, and never for a table that is the only copy.

The read-only query behind it

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

Query 4: storage by database
-- Finitizer Snowflake Cost Check, query 4 of 5: storage by database
-- sf-cost-check-v1 (2026-11-10). Read-only: it reads Account Usage and changes nothing.
-- Active, Time Travel, Fail-safe and clone-retained bytes per database, and how many
-- permanent tables hold more history than live data (the transient-table candidates).
-- Database names and totals only, no table names.
SELECT table_catalog AS database_name,
       COUNT(*) AS tables,
       SUM(active_bytes) AS active_bytes,
       SUM(time_travel_bytes) AS time_travel_bytes,
       SUM(failsafe_bytes) AS failsafe_bytes,
       SUM(retained_for_clone_bytes) AS retained_for_clone_bytes,
       COUNT_IF(is_transient = 'YES') AS transient_tables,
       COUNT_IF(is_transient = 'NO' AND NOT COALESCE(deleted, FALSE)
                AND time_travel_bytes + failsafe_bytes > active_bytes
                AND time_travel_bytes + failsafe_bytes > 1073741824) AS churn_tables,
       SUM(IFF(is_transient = 'NO' AND NOT COALESCE(deleted, FALSE)
               AND time_travel_bytes + failsafe_bytes > active_bytes
               AND time_travel_bytes + failsafe_bytes > 1073741824, time_travel_bytes, 0)) AS churn_time_travel_bytes,
       SUM(IFF(is_transient = 'NO' AND NOT COALESCE(deleted, FALSE)
               AND time_travel_bytes + failsafe_bytes > active_bytes
               AND time_travel_bytes + failsafe_bytes > 1073741824, failsafe_bytes, 0)) AS churn_failsafe_bytes,
       COUNT_IF(COALESCE(deleted, FALSE)) AS dropped_tables,
       SUM(IFF(COALESCE(deleted, FALSE), time_travel_bytes + failsafe_bytes, 0)) AS dropped_bytes
FROM snowflake.account_usage.table_storage_metrics
GROUP BY table_catalog
ORDER BY SUM(active_bytes + time_travel_bytes + failsafe_bytes + retained_for_clone_bytes) DESC;

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.