Normalisation vs Denormalisation
Normalisation and denormalisation are two opposing approaches to organising data. One reduces duplication for accuracy; the other accepts duplication for speed. Knowing the trade-off helps you understand design choices in your system.
Most business databases lean towards normalisation, with selective denormalisation where performance demands it.
Normalisation
A normalised database stores each fact in exactly one place. A customer's address lives in the customer table, and orders simply reference that customer. Update the address once and every order reflects it.
Denormalisation
A denormalised design deliberately copies some data to save the database from joining many tables together. It can make heavy reports much faster, at the cost of having to keep the copies in step.
| Aspect | Normalised | Denormalised |
|---|---|---|
| Duplication | Minimal | Accepted |
| Update safety | High | Lower |
| Read speed | Good | Often faster |
| Best for | Transactions | Reporting |
Frequently Asked Questions
Which does Progressive Robot prefer?
We normalise by default for safety, then denormalise only specific, measured hot spots — usually in reporting tables.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.