Third Normal Form (3NF) Definition
You'll learn: What Third Normal Form (3NF) is and why it requires eliminating transitive dependencies from a relation that's already in 2NF.
Understanding 3NF Requirements
A relation is in Third Normal Form (3NF) when:
- It is already in Second Normal Form (2NF), AND
- It has no transitive dependencies — meaning no non-key attribute depends on another non-key attribute.
Recall from earlier lessons that a transitive dependency occurs when attribute A determines B, and B determines C, creating an indirect path: A → B → C. In 3NF, every non-key attribute must depend directly on the candidate key, not through another non-key attribute.
Why This Matters
Think of 3NF as removing "middlemen" in your data dependencies. Imagine you have a table storing student information where:
StudentID → MajorMajor → DepartmentBuilding
This creates a transitive dependency: StudentID → Major → DepartmentBuilding. The building depends on the major, not directly on the student ID. This violates 3NF because DepartmentBuilding (a non-key attribute) depends on Major (another non-key attribute).
The Problem Without 3NF
Transitive dependencies cause:
- Update anomalies: Changing a major's building requires updating every student with that major
- Insertion anomalies: You can't record a major's building without having a student
- Deletion anomalies: Removing the last student in a major loses the building information
Checking for 3NF
To verify 3NF, examine each non-key attribute and ask: "Does this depend directly on the entire candidate key, or does it depend on another non-key attribute?" If the latter, you've found a transitive dependency.
Key Takeaway: Third Normal Form (3NF) requires a relation to be in 2NF with all transitive dependencies eliminated—every non-key attribute must depend only on candidate keys, not on other non-key attributes.