Complete Normalization Process
Prepared by: ___________________
Class: ___________________
Date: ___________________
Introduction
This document explains the full normalization process step-by-step: UNF → 1NF → 2NF
→ 3NF → BCNF. Each stage removes redundancy and anomalies while improving data
integrity.
Unnormalized Table (UNF)
Course_Code Course_Name Teacher_Name
RollNo Name System_Used Hourly_Rate Total_Hrs
C1 Visual Basic ABC 100,101,102,103 A1,A2,A3,A4 P-I,P-II 20,30 7,3
C2 Oracle&Dev DEF 100,104,107 A1,A5,A7 P-II,P-III 37,30 6,3
C3 C++ KJP 101,106,107 A2,A6,A7 P-IV,P-IV 40,40 1,3
C4 Java Kumar 108,109 A8,A9 P-I,P-I 20,20 2,2
Anomalies in UNF:
• Insertion: Cannot add course until a student joins it.
• Update: Changing teacher/course requires multiple updates.
• Deletion: Removing last student deletes course info.
First Normal Form (1NF)
In 1NF, multi-valued attributes are removed to ensure atomic values.
Course_Code Course_Name Teacher_Name
RollNo Name System_UsedHourly_Rate
Total_Hrs
C1 Visual Basic ABC 100 A1 P-I 20 7
C1 Visual Basic ABC 101 A2 P-II 30 3
C2 Oracle&Dev DEF 100 A1 P-II 37 6
C2 Oracle&Dev DEF 104 A5 P-III 30 3
Anomalies in 1NF:
• Insertion: Cannot add new course until a student joins.
• Update: Changing teacher/course requires multiple updates.
• Deletion: Removing last student deletes course info.
Second Normal Form (2NF)
In 2NF, partial dependencies are removed. Attributes depend on the whole primary key.
Course_Code Course_Name Teacher_Name
C1 Visual Basic ABC
C2 Oracle&Dev DEF
C3 C++ KJP
C4 Java Kumar
RollNo Name System_Used Hourly_Rate
100 A1 P-I 20
101 A2 P-II 30
102 A3 P-I 20
Course_Code RollNo Total_Hrs
C1 100 7
C1 101 3
C2 104 6
Anomalies in 2NF:
• Insertion: Cannot add system hourly rate until a student uses it.
• Update: Changing hourly rate requires multiple updates.
• Deletion: Removing last student using a system deletes its rate info.
Third Normal Form (3NF)
In 3NF, transitive dependencies are removed. Non-key attributes must depend only on
keys.
System_Used Hourly_Rate
P-I 20
P-II 30
P-III 37
P-IV 40
After 3NF, insertion, update, and deletion anomalies are removed.
Boyce-Codd Normal Form (BCNF)
BCNF handles cases where 3NF fails. Every determinant in the table must be a candidate
key, ensuring the highest level of normalization before moving to 4NF and 5NF.
Conclusion
This step-by-step normalization process transforms the unnormalized table into 1NF, 2NF,
3NF, and BCNF, eliminating redundancy and anomalies while maintaining data integrity
and efficiency.