Normalisation and when to break it
Normalising removes duplicated truth. Denormalising trades that safety for read speed, and should be a decision rather than an accident.
- 4m
- Intermediate
Video by DbSchema Database Designer · YouTube
Check your understanding
3 questions. Unlocks when you finish the video.
Overview
What this lesson covers
- Remove duplicated data and update anomalies
- Recognise when denormalisation is justified
- Model many-to-many relationships properly
This lesson sits in Schema Design, part of PostgreSQL for Developers. It assumes what came before it and leads directly into the next lesson in the module.
In this lesson you will:
- Remove duplicated data and update anomalies
- Recognise when denormalisation is justified
- Model many-to-many relationships properly
Resources
Your notes will live here
Note taking is not available yet. Nothing you type would be saved, so the tab stays read-only for now.