Third Normal Form (3NF)
What you'll learn: How to eliminate transitive dependencies between non-key attributes to reach 3NF and reduce redundancy even further.
The Core Idea
After achieving Second Normal Form (2NF), you've removed partial dependencies—but there's still one more type of redundancy to tackle. Third Normal Form (3NF) eliminates transitive dependencies, where a non-key attribute depends on another non-key attribute, which in turn depends on the primary key.
Think of it like a game of telephone: if Column C depends on Column B, and Column B depends on the primary key A, then Column C is transitively dependent on A. This creates unnecessary redundancy.
Understanding Transitive Dependencies
A transitive dependency exists when:
- You have a primary key (e.g.,
EmployeeID) - A non-key attribute depends on the key (e.g.,
DepartmentIDdepends onEmployeeID) - Another non-key attribute depends on that attribute (e.g.,
DepartmentNamedepends onDepartmentID)
The problem? DepartmentName doesn't directly depend on EmployeeID—it depends on DepartmentID. This creates redundancy: if multiple employees are in the same department, you're repeating DepartmentName unnecessarily.
Reaching 3NF
To achieve 3NF, split the table so every non-key attribute depends directly on the primary key, not on other non-key attributes.
Before 3NF (redundant):
- Employee table:
EmployeeID,Name,DepartmentID,DepartmentName
After 3NF:
- Employee table:
EmployeeID,Name,DepartmentID - Department table:
DepartmentID,DepartmentName
Now DepartmentName lives only where it logically belongs, eliminating update anomalies and redundancy.
Key Takeaway: Third Normal Form removes transitive dependencies by ensuring all non-key attributes depend directly on the primary key, not on other non-key attributes—reducing redundancy and simplifying data maintenance.