Scribd
Upload
7 views3 pages

Database Normalization Explained

Normalization is a process that organizes database data to minimize redundancy and enhance integrity. It involves several normal forms (1NF, 2NF, 3NF, BCNF) that address specific data issues such as redundancy, update anomalies, and transitive dependencies. The document provides examples of normalization steps from an unnormalized table to various normal forms, illustrating how to eliminate data anomalies.

Uploaded by

sarimullahbaig.2010
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views3 pages

Database Normalization Explained

Normalization is a process that organizes database data to minimize redundancy and enhance integrity. It involves several normal forms (1NF, 2NF, 3NF, BCNF) that address specific data issues such as redundancy, update anomalies, and transitive dependencies. The document provides examples of normalization steps from an unnormalized table to various normal forms, illustrating how to eliminate data anomalies.

Uploaded by

sarimullahbaig.2010
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Database Normalization — A Level Notes

What is Normalization?
Normalization is a process of organizing data in a database to reduce data redundancy and
improve data integrity. It ensures that data is stored logically and consistently.

Why Normalize a Database?


Problem Example Effect

Redundancy Same student address Wastes space


repeated in multiple
records

Update Anomaly Changing a student’s Inconsistency risk


address requires multiple
updates

Insertion Anomaly Can’t add a course unless a Missing data


student is enrolled

Deletion Anomaly Deleting a student removes Data loss


course information

Normal Forms Overview


Normal Form Condition Removes

1NF No repeating groups; Repetition


atomic values only

2NF In 1NF and every non-key Partial dependency


attribute depends on the
whole key

3NF In 2NF and no transitive Transitive dependency


dependency

BCNF Every determinant is a Complex anomalies


candidate key

Example: Step-by-Step Normalization

Unnormalized Table
StudentCourse Table (Unnormalized):
StudentID StudentName Course1 Course2 Course3

S1 Ali Khan DBMS OS None

S2 Sara Ahmed Python AI None

Problem: Repeating groups and difficult updates.

1NF (First Normal Form)


Each field contains atomic values only.

StudentID StudentName Course

S1 Ali Khan DBMS

S1 Ali Khan OS

S2 Sara Ahmed Python

S2 Sara Ahmed AI

2NF (Second Normal Form)


In 1NF, but no partial dependency (non-key attributes depend on the whole key). Split
StudentName into a separate table.

Students Table:

StudentID StudentName

S1 Ali Khan

S2 Sara Ahmed

Enrollments Table:

StudentID Course

S1 DBMS

S1 OS

S2 Python

S2 AI

3NF (Third Normal Form)


No transitive dependency.

Example: Department and DeptHead should be in a separate table.


Students Table:

StudentID StudentName Department

S1 Ali Khan CS

S2 Sara Ahmed IT

Departments Table:

Department DeptHead

CS Dr. Aslam

IT Mr. Kamal

BCNF (Boyce-Codd Normal Form)


Every determinant must be a candidate key. Example of Course-Instructor-Room.

Courses Table:

Course Instructor

DBMS Dr. Aslam

OS Dr. Kamal

Instructors Table:

Instructor Room

Dr. Aslam R101

Dr. Kamal R102

Summary Table
Normal Form Key Idea Problem Eliminated

1NF Atomic values, unique rows Repetition

2NF Full functional dependency Partial dependency

3NF No transitive dependency Indirect dependency

BCNF Every determinant is a key Complex anomalies

You might also like