Database Normalization: From 1NF to 2NF
Presented by Group 2A
October 2, 2025
Presented by Group 2A 1NF to 2NF October 2, 2025 1 / 11
What is First Normal Form (1NF)?
1NF is the foundation of relational database design. A table is in 1NF if:
All attributes contain atomic (indivisible) values
There are no repeating groups or arrays
Each row is uniquely identifiable
Example: Denormalized → 1NF
Before (Not 1NF) After (1NF)
Student Courses Student Course
Alice Math, CS Alice Math
Bob Physics Alice CS
Bob Physics
Presented by Group 2A 1NF to 2NF October 2, 2025 2 / 11
Problems with 1NF
Even in 1NF, databases can suffer from:
Partial dependencies
Update anomalies
Insert anomalies
Delete anomalies
Example: In a table with composite key (S tude nt, Course):
I n s t r u c t o r depends only on Course
Updating an instructor requires updating all rows for that course
Presented by Group 2A 1NF to 2NF October 2, 2025 3 / 11
What is Second Normal Form (2NF)?
A relation is in 2NF if:
1 It is already in 1NF
2 No non-prime attribute is partially dependent on any candidate
key
Key concept: Eliminate partial dependencies
Composite Key(A, B)
Non-primeAttribute C
Presented by Group 2A 1NF to 2NF October 2, 2025 4 / 11
Step-by-Step: 1NF → 2NF
Step 1: Identify functional dependencies
StudentID → StudentName
CourseID → CourseName, I n s t r u c t o r
(S tude ntID , CourseID) → all attributes
Step 2: Identify partial dependencies
StudentName depends only on StudentID
CourseName, I n s t r u c t o r depend only on CourseID
Presented by Group 2A 1NF to 2NF October 2, 2025 5 / 11
Step 3: Decompose into new tables
Students Courses
ID Name ID Name Instructor
S1 Alice C1 Math Dr. Smith
S2 Bob C2 CS Dr. Jones
Enrollments
StudentID CourseID
S1 C1
S1 C2
S2 C1
Presented by Group 2A 1NF to 2NF October 2, 2025 6 / 11
Real-world Example: Employee-Project
EmpID Name Dept ProjID ProjName Hours
1NF Table: E1 Alice IT P1 Website 20
E1 Alice IT P2 DB 15
Functional Dependencies:
EmpID → Name, Dept
ProjID → ProjName
⇒ Partial dependencies!
Presented by Group 2A 1NF to 2NF October 2, 2025 7 / 11
Normalize to 2NF
Decompose into:
Employees(EmpID, Name, Dept)
P r o j e c t s ( P r o j I D , ProjName)
Assignments(EmpID, P r o j I D , Hours)
Benefits:
No redundant data
Update employee info once
Add employees without projects
Presented by Group 2A 1NF to 2NF October 2, 2025 8 / 11
Benefits of 2NF
Reduced redundancy
Improved data integrity
Elimination of anomalies
Clearer relationships
Presented by Group 2A 1NF to 2NF October 2, 2025 9 / 11
Conclusion
1NF: Atomic values, no repeating groups
2NF: Remove partial dependencies
Process: Identify FDs Decompose tables
Questions?
Presented by Group 2A 1NF to 2NF October 2, 2025 10 / 11
Thank You!
Questions & Discussion
References:
Codd (1970)
Elmasri & Navathe
Date (2003)
Presented by Group 2A 1NF to 2NF October 2, 2025 11 / 11
