Database Normalization and Normal Forms

Database normalization is a systematic process of organizing data in a relational database to reduce redundancy and improve data integrity. It involves dividing large tables into smaller, related ones and defining relationships between them. Normalization ensures that the database is efficient, consistent, and easier to maintain.

---

🌍 Why Normalize a Database?

• Reduce redundancy: Avoid storing duplicate data.
• Prevent anomalies: Minimize insert, update, and delete anomalies.
• Improve consistency: Ensure data integrity across tables.
• Enhance scalability: Make schema easier to evolve and maintain. DigitalOcean

---

🏛️ Normal Forms

Normalization is achieved through a series of normal forms, each stricter than the previous.

First Normal Form (1NF)

• Each column must contain atomic (indivisible) values.
• No repeating groups or arrays.

-- Not normalized
Student(ID, Name, Subjects)

-- Normalized
Student(ID, Name)
Subjects(StudentID, Subject)

Second Normal Form (2NF)

• Must be in 1NF.
• No partial dependency: Non-key attributes must depend on the whole primary key.

-- Example: Splitting composite key dependencies
Orders(OrderID, ProductID, Quantity)
Products(ProductID, ProductName)

Third Normal Form (3NF)

• Must be in 2NF.
• No transitive dependency: Non-key attributes should depend only on the primary key.

-- Example: Remove dependency through another non-key attribute
Employee(EmpID, EmpName, DeptID)
Department(DeptID, DeptName)

Boyce-Codd Normal Form (BCNF)

• A stricter version of 3NF.
• Every determinant must be a candidate key.

Fourth Normal Form (4NF)

• Must be in BCNF.
• No multi-valued dependencies.

Fifth Normal Form (5NF)

• Must be in 4NF.
• Deals with join dependencies, ensuring tables cannot be decomposed further without losing information. GeeksForGeeks

---

📊 Comparison of Normal Forms

Normal Form	Key Rule	Goal
1NF	Atomic values, no repeating groups	Basic structure
2NF	No partial dependency	Eliminate redundancy from composite keys
3NF	No transitive dependency	Ensure attributes depend only on primary key
BCNF	Every determinant is a candidate key	Stronger consistency
4NF	No multi-valued dependency	Avoid complex redundancy
5NF	No join dependency	Maximum normalization

---

📖 Conclusion

Database normalization is essential for designing efficient and reliable relational schemas. By progressively applying normal forms (1NF → 5NF), developers reduce redundancy, prevent anomalies, and ensure data integrity. While higher normal forms improve consistency, they may also increase complexity—so practical database design often balances normalization with performance needs. FreeCodecamp