Warehouse Model Cleanup: Retire dbt Models Nobody Reads

Warehouse model cleanup starts when transformation graphs keep building marts, staging tables, or semantic models that no dashboard, export, experiment, or analyst notebook reads anymore.

The useful output is a warehouse model cleanup pull request with lineage proof, usage evidence, removed schedules, test updates, and owner approval. Keep the review concrete: Disable schedules or reduce materialization before deleting shared models, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when dropping a model that still feeds a downstream dashboard.

Key takeaways

Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
Use one analytics reporting cycle plus month-end and stakeholder review windows before deciding that “quiet” means “unused.”
Prefer reversible changes first when dropping a model that still feeds a downstream dashboard is still plausible.
Leave behind a warehouse model cleanup pull request with lineage proof, usage evidence, removed schedules, test updates, and owner approval so the next review starts with context.
Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.

Map Warehouse Lineage

Start with one warehouse model family across lineage graphs, scheduled runs, tests, exposures, dashboards, docs, owners, and query logs. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.

Field	Why it matters
Owner	Cleanup needs a person or team that can accept the decision
Current purpose	A short reason to keep the item, written in present tense
Last meaningful use	read/write activity, size, query plans, job dependencies, and retention rules
Dependency evidence	database metrics, query logs, application references, and reporting schedules
Risk if wrong	The outage, data loss, access failure, or rollback gap the review must avoid
Next action	Keep, reduce, archive, disable, remove, or investigate

Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.

Model Evidence to Collect

The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For warehouse model cleanup, collect enough evidence to answer that without relying on naming conventions.

Check	What to look for	Cleanup signal
Lineage position	upstream sources, downstream models, exposures, dashboards, and reverse dependencies	The model is a leaf or its consumers are obsolete
Run cost and freshness	job duration, warehouse credits, failures, row counts, and freshness alerts	The model spends compute without supporting a current decision
Consumer proof	query logs, BI usage, notebooks, exports, and stakeholder owners	No active consumer reads or validates the model
Semantic replacement	new model, metric definition, contract, tests, and documentation	Business meaning survives after cleanup

Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.

If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.

Disable Schedules First

Use the least permanent move that proves the decision. In warehouse model cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.

Disable schedules or reduce materialization before deleting shared models.
Remove tests, docs, exposures, and dashboards with the model they describe.
Keep a revert path and compiled SQL for one warehouse release.

Track the cleanup candidate with a simple priority score:

Score	Good sign	Bad sign
Impact	Meaningful spend, risk, toil, noise, or confusion disappears	The item is cheap and low-risk but politically distracting
Confidence	Owner, purpose, and dependency path are understood	The team is guessing from age or name
Reversibility	Restore, recreate, re-enable, or rollback path exists	Deletion would be the first real test
Prevention	A rule can stop recurrence	The same pattern will return next month

Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.

Models Behind Decisions

Some cleanup candidates are supposed to look quiet. Do not rush these cases:

Finance metrics, executive dashboards, ML features, and customer-facing analytics.
Models used indirectly through semantic layers or copied SQL.
Source freshness and data quality tests that live on the stale model.

For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.

Run the Model Cleanup

Run warehouse model cleanup as a decision review, not an open-ended hygiene project.

Pick the narrow scope and export the candidate list.
Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
Apply the least permanent useful change first.
Watch the signals that would reveal a bad decision.
Complete the final removal only after the review window closes.
Save a warehouse model cleanup pull request with lineage proof, usage evidence, removed schedules, test updates, and owner approval.

For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.

Give Models Review Dates

Prevention should change the creation path, not just the cleanup path. For warehouse model cleanup, the useful prevention fields are data owner, retention policy, recreate path, and review date. Make those fields part of normal creation and review.

Create models with owner, decision served, materialization reason, and review date.
Treat unused exposures and zero-reader models as cleanup candidates.
Review model lineage after dashboard, metric, and source migrations.

The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.

Example Decision Record

Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.

Field	Example entry for this cleanup
Candidate	Stale warehouse transformation models in analytics engineering projects
Why it looked stale	Low recent activity, unclear owner, or no current consumer after the first review
Evidence checked	Lineage position, Run cost and freshness, and owner confirmation
First reversible move	Disable schedules or reduce materialization before deleting shared models
Watch signal	The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong
Final action	Keep, reduce, archive, disable, or remove after one analytics reporting cycle plus month-end and stakeholder review windows
Prevention rule	Create models with owner, decision served, materialization reason, and review date

This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.

FAQ

How often should teams do warehouse model cleanup?

Use one analytics reporting cycle plus month-end and stakeholder review windows for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.

What is the safest first action?

The safest first action is usually ownership repair plus evidence collection. After that, disable schedules or reduce materialization before deleting shared models. That creates a visible test before permanent deletion.

What should not be removed quickly?

Do not rush anything connected to finance metrics, executive dashboards, ml features, and customer-facing analytics. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.

How do you make the decision useful later?

Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.