Snowflake Permanent Table with Large Fail-safe
A permanent table carries seven days of Fail-safe storage that you cannot query or switch off, billed on top of Time Travel.
Free to start. No card. The playground just needs your work email.
Snowflake
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Snowflake, with read-only access to the account.
Explain
Every finding says exactly what to change: Move the large permanent table to a transient table.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Snowflake Table on Snowflake
- The fix, by hand
- Confirm the resource is regenerable (staging, ELT intermediate, scratch).
- Recreate as TRANSIENT to drop Fail-safe storage:.
- Confirm FAILSAFE_BYTES = 0 on the new table after a maintenance pass.
- Reserve permanent tables for source-of-truth. TRANSIENT has at most 1-day Time Travel and zero Fail-safe.
These are the steps the finding carries in the product.
- Category
- Governance. Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-2109- Full reference
Related checks
See the governance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.