Bloated Storage
Find development, test, and backup databases and schemas that pay for Time Travel storage they don't need, and turn it off to cut storage spend.
Overview
Bloated Storage identifies development, test, staging, and backup databases and schemas in Snowflake that keep Time Travel history. Time Travel is a Snowflake feature that keeps previous versions of changed or deleted data for a set number of days (the retention period), so you can query or restore it. That history is billed as storage. In non-production environments it is rarely needed, so setting the retention period to 0 days removes the cost.
How It Works
Detection Logic
Seemore identifies non-production databases and schemas — such as development, staging, sandbox, testing, and backup environments — based on common naming conventions.
A non-production asset is flagged when:
Time Travel is enabled — for databases, the retention period is greater than 0 days.
Time Travel storage has a cost — the asset holds Time Travel data that you are billed for. Assets with no Time Travel storage are skipped.
If a database is flagged, its schemas are not flagged separately — the database-level change covers them.
Savings Estimation
Each insight includes:
Current retention period and the recommended value (0 days).
Estimated annual storage savings, based on the asset's current Time Travel storage and your Snowflake storage price per TB.
Remediation
Confirm the database or schema is not production and that nobody relies on restoring its data with Time Travel or
UNDROP.Run the SQL provided in the insight in a Snowflake worksheet, for example:
For a schema, the insight provides the equivalent
ALTER SCHEMAstatement.Mark the insight as Done in Seemore.
Database insights close automatically once Seemore sees the retention period set to 0 or the database dropped.
Configuration
Analysis window
30 days
Period used to calculate Time Travel storage cost, annualized for the savings estimate.
Last updated
