Skip to content
Finitizer
To investigate

Snowflake clone-retained storage: bytes kept for clones

A zero-copy clone shares storage with its source until either one changes.

When the source is rewritten or dropped, the bytes the clone still needs stay on the bill.

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

RETAINED_FOR_CLONE_BYTES by database, from TABLE_STORAGE_METRICS, beside the Time Travel and Fail-safe of tables that churn.

Why it costs money

  • Cloning is free at first, because the clone points at the same micro-partitions.
  • As the source table changes, its old partitions are kept for the clone, and they bill as storage of the source.
  • Old development and test clones are often forgotten long after their source has been rebuilt.

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 shows clone-retained bytes as part of storage and raises them alongside the transient table check. It claims no saving of its own.

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

In the sample report

Clone-retained storage

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. 1List clones that are no longer used, starting with development and test databases.
  2. 2Drop the clones nobody needs. The retained bytes then go through Time Travel and Fail-safe like any deleted data.

How to tell it worked. Read RETAINED_FOR_CLONE_BYTES again after Time Travel and Fail-safe have passed.

Trade-offs. A dropped clone can only be restored within its own Time Travel period.

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.