Databases
Database Stored Procedure Cleanup: Retire Routines Nobody Calls
Stored procedure cleanup starts where database routines bypass normal application ownership. A routine may still be called by reports, batch jobs, support tools, ETL tasks, or old release branches even after product code stopped referencing it.
The useful output is a stored procedure retirement record with caller evidence, grant changes, replacement contract, test output, and restore script. Keep the review concrete: Deprecate or wrap the routine before dropping public database contracts, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when breaking batch jobs or reports that call routines directly.
Key takeaways
- Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
- Use one reporting and batch-job cycle plus any finance or audit close window before deciding that “quiet” means “unused.”
- Prefer reversible changes first when breaking batch jobs or reports that call routines directly is still plausible.
- Leave behind a stored procedure retirement record with caller evidence, grant changes, replacement contract, test output, and restore script so the next review starts with context.
- Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.
Map Routine Callers
Start with one database routine family across grants, job schedulers, application callers, reporting tools, migration scripts, and schema contracts. 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.
Procedure 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 stored procedure cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Callers | Query logs, scheduled jobs, BI tools, app code, support scripts, and old release branches | No supported caller executes the routine |
| Privilege surface | EXECUTE grants, definer rights, service accounts, and cross-schema access | The routine grants access no current workflow needs |
| Result contract | Output columns, side effects, temp tables, and downstream reports | Consumers have a replacement with equivalent behavior |
| Retirement path | Deprecation notice, wrapper routine, test query, and restore script | Removal can be staged without surprising direct database users |
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.
Example Evidence Check
Start with routine metadata, then pair it with query logs or scheduler references.
SELECT routine_schema, routine_name, routine_type, data_type, last_altered
FROM information_schema.routines
WHERE routine_schema NOT IN ('information_schema', 'pg_catalog')
ORDER BY last_altered;Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.
Deprecate Database Contracts
Use the least permanent move that proves the decision. In stored procedure 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.
- Deprecate or wrap the routine before dropping public database contracts.
- Remove grants separately from implementation deletion when caller risk is unclear.
- Keep a restore script until reports and jobs have passed their review window.
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.
Routines That Run Quietly
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- Finance close, support repair, compliance export, and migration routines.
- Procedures with elevated definer rights or cross-schema writes.
- BI dashboards that call the database directly without repository references.
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 Routine Retirement
Run stored procedure 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 stored procedure retirement record with caller evidence, grant changes, replacement contract, test output, and restore script.
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.
Register Shared Routines
Prevention should change the creation path, not just the cleanup path. For stored procedure cleanup, the useful prevention fields are data owner, retention policy, recreate path, and review date. Make those fields part of normal creation and review.
- Register routines with owner, caller list, privilege reason, and review date.
- Prefer versioned routines or explicit API endpoints for shared contracts.
- Review grants and query logs after application workflow 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 stored procedures in database-backed applications |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Callers, Privilege surface, and owner confirmation |
| First reversible move | Deprecate or wrap the routine before dropping public database contracts |
| 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 reporting and batch-job cycle plus any finance or audit close window |
| Prevention rule | Register routines with owner, caller list, privilege 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 stored procedure cleanup?
Use one reporting and batch-job cycle plus any finance or audit close window 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, deprecate or wrap the routine before dropping public database contracts. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to finance close, support repair, compliance export, and migration routines. 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.