Why Tables Need a Reason to Exist
Every table in your database should answer a simple question: what business need does this entity serve? Without a documented purpose, tables become dumping grounds for data that nobody understands.
Defining table purpose is the first step in schema-intent design. It forces architects to articulate the business value of each entity before any columns are created. This clarity prevents structural drift, where tables accumulate columns over time that have nothing to do with their original intent.
Questions to Define Table Purpose
Ask these questions before creating any new table.
What Business Need Does This Serve?
Identify the specific product, process, or reporting requirement that demands this entity. If you cannot name it, the table may not be needed.
Is This a Separate Entity?
Could this data live inside an existing table? Splitting entities too aggressively creates unnecessary joins; merging unrelated data creates confusion.
Will This Purpose Change?
Consider whether the business need is stable or evolving. Tables built for temporary needs should be designed differently from permanent entities.
Who Will Query This Table?
Different consumers have different access patterns. Knowing who reads the data helps you decide on indexes, denormalisation, and access controls.
When Will This Data Expire?
Define the data lifecycle. Some tables hold transactional records that must persist forever; others hold transient state that should be purged regularly.
How Will This Be Documented?
Write the purpose statement in the table's comment or your schema documentation tool. Future developers should find it without asking.
Purpose Statement Template
For every table, write a one-sentence purpose statement using this template:
"The [table_name] table stores [data type] to support [business process], accessed by [consumers], with a retention period of [duration]."
Keep this statement in your schema documentation and review it during every migration. If a proposed change does not align with the stated purpose, either the change or the purpose statement needs updating.
Ready to review your table purposes?
Explore related materials and continue your schema-intent review.