Scribd
Upload
2 views14 pages

Normalization

Normalization is a process in database design aimed at reducing data redundancy and improving data integrity by organizing tables into higher normal forms. The document outlines the characteristics and requirements of various normal forms, including 1NF, 2NF, 3NF, BCNF, 4NF, and 5NF, providing examples for each. Proper normalization ensures atomic values, absence of redundancy, and minimal loss of information.

Uploaded by

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

Normalization

Normalization is a process in database design aimed at reducing data redundancy and improving data integrity by organizing tables into higher normal forms. The document outlines the characteristics and requirements of various normal forms, including 1NF, 2NF, 3NF, BCNF, 4NF, and 5NF, providing examples for each. Proper normalization ensures atomic values, absence of redundancy, and minimal loss of information.

Uploaded by

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

DATABASE Manish joshi

Parul Institute of Computer


NORMALIZATION Applications
WHAT IS NORMALIZATION?
This is the process which allows you to remove redundant data
within your database.
This involves restructuring the tables to successively meet
higher forms of Normalization.
A properly normalized database should have the following
characteristics
Atomic values in each fields
Absence of redundancy.
Minimal use of null values.
Minimal loss of information.
FIRST NORMAL FORM (1NF)
• Each column must have only atomic values
Roll_no Name Subjects
101 Rahul OS,JAVA
102 Priya CN,DS
103 Kiran OS

Roll_no Name Subjects


101 Rahul OS
101 Rahul JAVA
102 Priya CN
102 Priya DS
103 Kiran OS
SECOND NORMAL FORM (2NF)
• Table must be in 1 NF
• It should not have partial dependency
•Partial Dependency – Proper subset of candidate key determines non key attribute.

Roll_no Course_no Course_fee


101 1001 1000 {roll_no,course_no} is the
102 1002 3000 candidate key
101 1004 5000
103 1005 3000
• Multiple courses are having same fees
• Course_fee can not decide value of course_no or roll_no
• COURSE_FEE together with roll_no cannot decide the value of COURSE_NO
• COURSE_FEE together with COURSE_NO cannot decide the value of roll_no
2NF
Roll_no Course_no
101 1001
102 1002
101 1004
103 1005

Course_no Course_fees
1001 1000
1002 3000
1004 5000
1005 3000
THIRD NORMAL FORM (3NF)
Table must be in 2NF
There is no transitive dependency for non key attributes.
A->B & B->C then A->C
Stud_no is the candidate
key

STUD_NO -> STUD_STATE and STUD_STATE -> STUD_COUNTRY are


true.
So STUD_COUNTRY is transitively dependent on STUD_NO.
3NF

Stud_no Stud_name Stud_state Stud_age


…

State country
…
BOYCE CODD NORMAL FORM
(BCNF)
Table must be in 3NF
For every X->Y , X is superkey Roll_no + subject is the primary key
Roll_no Subject Professor
101 Java Mr. J1
101 OS Mr. O
102 Java Mr. J2

{roll_no,subject} ->professor
Professor->subject (professor is not super key)
BCNF
Roll_no Subject Professor
101 Java Mr. J1
101 OS Mr. O
102 Java Mr. J2

Roll_no Prof_id Prof-id Professor Subject


101 P1 P1 Mr. J1 Java
101 P2 P2 Mr. O OS
102 P3 P3 Mr. J2 Java
FOURTH NORMAL FORM (4NF)
Table must be in BCNF
It should not have Multivalued Dependency.
4NF
4NF
FIFTH NORMAL FORM (5NF)
. Fifth normal form is satisfied when all tables are divided into as many tables as
possible in order to avoid redundancy. Once it is in fifth normal form it cannot be
broken into smaller relations without changing the facts or the meaning.
THANK YOU

You might also like