Skip to content
BENIBIX Learn

Database Normalization

Development🗃️ DatabasesRelational Databases

Also known as Normalization, Normal Form, Normalisation

Setting up a database so each fact is kept in one place.

Think of it like

Think of it like one phone book for the whole house. Change a number once, and it is right for all.

Example

Jack's orders table copied each buyer's address. When Lucy moved, half her orders showed the old one. Moving addresses to the customers table fixed it.

Why it matters

Copied data drifts apart. When there is just one copy, it cannot.

Definition

Normalization means each fact is kept in just one place in a database. Instead of copying a customer's city into every order, you keep it in the customers table and link to it. That way, a change happens once and nothing gets out of step. The rules come in steps called normal forms, such as first, second and third. Most apps aim for third normal form.

Common mistake

Splitting tables so far that every page needs ten joins. Sometimes a small copy is worth it for speed.

Key takeaways

  1. 1
    One fact, one place. No copies to drift apart.
  2. 2
    Link, do not copy. Keys point to the one copy.
  3. 3
    Third form is enough. Most apps stop there.

Compare