Snowflake Stale Stage
Files left in the stage are billed as storage indefinitely, and a stage nobody loads from usually marks a pipeline that has moved elsewhere.
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: Delete the stale stage.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Snowflake Stage on Snowflake
- The fix, by hand
- Open Snowsight → Data → Stages → the resource and list its contents (LIST @the resource;).
- Identify stale staged files (last COPY long ago, files no longer referenced by any pipeline).
- REMOVE @the resource/‹path›, or REMOVE @the resource pattern='.*' for full purge.
- Update the source pipeline to use COPY INTO ... PURGE = TRUE so files self-clean after load.
- If the stage is fully orphaned: DROP STAGE the resource.
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-2111- 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.