Computer Science · A3.2 Database Design

A3.2.7 — Denormalization: When and Why to Break the Rules

Preview

IB DP Computer Science — A3 Databases — Database design | SL | A3.2.7

📋 What You Will Learn

  • Define denormalization and distinguish it from simply "not normalizing"
  • Explain why reads on a normalized database cost more: multi-table joins
  • Describe the main denormalization techniques: duplicated columns, precomputed values, merged and summary tables
  • State the advantages and disadvantages of both normalized and denormalized designs
  • Evaluate whether a given scenario justifies denormalization, weighing query simplicity against redundancy risk

⚖️ Why This Matters A café could keep its menu in one place behind the counter (one copy, always consistent, but every customer walks up to read it) — or print it on every table (instant to read, but a price change means reprinting them all and hoping none is missed). That is exactly the normalization/denormalization trade-off: one authoritative copy

Continue reading the full note