normalisation
Designing tables so each fact is stored in exactly one place, by splitting repeated data into related tables.
In more detail
A normalised design avoids copies that can disagree, such as a customer's city repeated on every order line. The steps are called normal forms: first, second and third. Joins then rebuild the combined view whenever you need it.
Related terms
- first normal form — The rule that every column holds a single value and a table has no repeating groups of columns or lists packed into one cell.
- second normal form — The rule that, in a table with a composite key, every other column depends on the whole key and not on just part of it.
- third normal form — The rule that every non-key column depends directly on the key, not on another non-key column.
- denormalisation — Deliberately storing a copy of data in a second place, usually to make reads faster by avoiding a join.
Taught in
- Inner Joins And Table Aliases — PostgreSQL, Indexing & Relational Data Modeling
- Normalisation To Third Normal Form — PostgreSQL, Indexing & Relational Data Modeling