Retire tables and models that nothing queries
Warehouse objects nothing has queried in a quarter, removed on the evidence of the query log.
The ticket
Remove warehouse tables and models that nothing has queried, backed by the query log.
Acceptance criteria
- Query-log evidence covering at least a quarter is attached
- Downstream dependencies are checked, not just direct queries
- Objects are deprecated before deletion, with a stated window
- Storage and compute savings are recorded
What lands as proof
Query-log evidence over a full quarter, which is the only defensible basis for dropping a table.
Why teams defer it
- Somebody might be querying it from a notebook nobody knows about, and that fear alone stops the work.
- Quarterly reporting means a quarter of silence is not proof, which pushes the safe window out further.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove warehouse tables and models that nothing has queried, backed by the query log. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means query-log evidence attached before anything is dropped, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.