A database is never just a database. It is a timeline with indexes.
Reading Pinal Dave’s post about the seven tables that seem to appear in every database made me laugh, then check a few schemas. That is an unfair thing for an article to do before lunch.
The joke works because the pattern feels true: databases collect decisions after the person who made them has moved on. A temporary table becomes infrastructure. A spreadsheet import becomes a payment rule. A flag nobody understands becomes load-bearing because one bad experiment taught everyone to leave it alone.
Every Name Leaves Evidence
Naming is usually treated as a small implementation detail. In older systems, names are evidence.
_new means two versions existed at once. backup means somebody was afraid to delete something. tmp means a deadline won. A person’s initials mean the object outlived its owner.
This is why database cleanup feels harder than deleting unused code. The code has a caller. The table has a story, and stories make people cautious.
The Risk Is Not Just Clutter
The obvious problem is mess. The more serious one is uncertainty.
When nobody knows which Customers table the application reads, or why a setting must remain 1, every future change carries a tax. Engineers search, guess, avoid, and add another layer instead of removing the old one. The schema gets safer to ignore and harder to understand.
It also turns operations into folklore. “Don’t touch that” may protect the system. It may also protect a broken workaround from ever being examined. Both look identical from the outside.
Cleanup Needs a Way Back
The answer is not to open a production console and delete anything with tmp in its name. That is how you create the next article.
A safer cleanup process needs an owner, dependency checks, usage evidence, a documented replacement, and a rollback or retention window. If nobody can explain an object, the first action should be to record that uncertainty, not hide it with another Archive_2026 table.
Maybe then database maintenance stops being a spring-cleaning exercise and becomes a form of institutional memory.
The Schema Remembers
The article is funny because it turns technical debt into characters. The joke lands because those characters are familiar. Most of us have inherited at least one table that looked temporary, important, mysterious or all three.
The uncomfortable part is that we are also creating the next generation of them.
A database records more than data. It records what a team feared, postponed, imported at 4:00pm and never explained.
That makes naming, ownership and deletion decisions less like housekeeping and more like leaving notes for people we will never meet.