What Is Database Normalization? 1NF, 2NF, 3NF Explained
Database normalization organizes tables to reduce redundancy and avoid update anomalies. Learn the first three normal forms with simple examples.
Published September 19, 2026
Normalization organises tables to remove duplicated data and prevent update anomalies. 1NF removes repeating groups, 2NF removes partial dependencies, and 3NF removes transitive dependencies.
The concept
1NF: every column holds a single atomic value and each row is unique. 2NF: every non-key column depends on the whole primary key (matters with composite keys). 3NF: non-key columns depend only on the key, not on other non-key columns.
The goal: store each fact once. The cost: more tables and more joins, so reporting databases sometimes denormalise on purpose.
One orders table becomes three
- Unnormalised: orders(id, customer_name, customer_city, items='shoe,hat')
- 1NF: split the items list into one row per item
- 2NF/3NF: move customer data to customers(id, name, city)
- Result: orders → customers, order_items → products
Practical examples
Violates 3NF
orders(id, customer_id, customer_city) -- city depends on customer, not orderFixed
customers(id, name, city)
orders(id, customer_id)Update anomaly avoided
A city change is one UPDATE on customers instead of many on orders.
UPDATE customers SET city = 'Pune' WHERE id = 7;Common mistakes
- Storing comma-separated lists in one column.
- Copying the customer's name into every order, leaving stale data.
- Over-normalising reporting tables.
Key takeaways
- 1NF atomic, 2NF whole key, 3NF only the key.
- Store each fact once.
- Denormalise only with a measured reason.
FAQ
What is BCNF?
A stricter version of 3NF that requires every determinant to be a candidate key.
Is higher always better?
No; 3NF is the practical target for most OLTP systems.