---
answer: direct
beat: system-design
source: 1 article · updated: November 14, 2026
---

Should every table have a surrogate primary key?

Usually yes: a compact, stable, meaningless key avoids cascading updates when business data changes. Keep a unique constraint on the natural identifier too, such as an email or SKU, so the database still prevents duplicates the surrogate key would let through.

Answered in

Relational Schema Design That Survives Contact With Production

Keys, relationships, constraints and indexes: the schema decisions that decide integrity and speed, with worked SQL for one-to-many and many-to-many.

Crashtech Editorial November 14, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.