Normalization organizes tables to reduce duplicated data and prevent update anomalies, where changing one fact means editing many rows.
Starting table
Enrollments(StudentID, StudentName, Courses, InstructorName, InstructorPhone), where Courses holds a comma-separated list like “DB101, OS201”.
First normal form (1NF)
Every column holds one atomic value and there are no repeating groups. Split the course list so each row holds one course: Enrollments(StudentID, CourseID, StudentName, CourseName, InstructorName, InstructorPhone), with the key (StudentID, CourseID).
Second normal form (2NF)
1NF, plus no column depends on only part of a composite key. StudentName depends only on StudentID, and the course details depend only on CourseID. Split them out:
Students(StudentID, StudentName)Courses(CourseID, CourseName, InstructorName, InstructorPhone)Enrollments(StudentID, CourseID)
Third normal form (3NF)
2NF, plus no column depends on another non-key column. InstructorPhone depends on the instructor, not the course. Move it:
Instructors(InstructorID, InstructorName, InstructorPhone)Courses(CourseID, CourseName, InstructorID)
Practice
Orders(OrderID, CustomerID, CustomerCity, OrderDate) breaks which normal form?
3NF: CustomerCity depends on CustomerID, a non-key column. Move it to a Customers table.