NORMALIZATION

ON DATA TABLES
3RD NORMAL FORM
THE PROBLEM
• technique for producing a set
What is of relations with desirable
NORMALIZATION? properties, given the data
requirements of an enterprise.

Who developed? • E.F. Codd (1972)

• It reduces data redundancies

Why
and helps eliminate the data
NORMALIZATION? anomalies.
BACKGROUND INFORMATION

• What is your research?

• How did you discover this problem?
• How did you get information to research this problem and attempt to solve it?
• Interviews?
• Personal experience?
• Internet/Books?
• Other ways?
 WORKABLE SOLUTIONS

Solution Solution Solution

#1 #2 #3
●
What materials does this ●
What materials does this ●
What materials does this
solution require? solution require? solution require?
●
What would this solution ●
What would this solution ●
What would this solution
look like (drawing, pictures, look like (drawing, pictures, look like (drawing, pictures,
text)? text)? text)?
●
What are some barriers you ●
What are some barriers you ●
What are some barriers you
might come across with this might come across with this might come across with this
solution? solution? solution?
 2NF IS NOT GOOD
ENOUGH
Definitely In 2NF…
• Problem – data still redundant
• Anomalies on insert, delete, modify
• Caused because table is really about more
than one thing
• Transitive dependency is the root of
the problem.
THIRD NORMAL FORM
(3NF)
The ff are the conditions that the table design is in 3NF..
• The table must be in 2NF
• Transitive functional dependency of attributes on any
super key must be removed.
CONVERSION TO THIRD
NORMAL FORM
•Create a separate table with attributes in a transitive
functional dependence relationship.
• Any determinant (LHS of FD) gets its own table
• Any attributes dependent on it (RHS of FD) go in that table
• Remove dependent attributes from the previous table

PROJECT (PROJ_NUM, PROJ_NAME)

ASSIGN (PROJ_NUM, EMP_NUM, HOURS)
EMPLOYEE (EMP_NUM, EMP_NAME, JOB_CLASS)
JOB (JOB_CLASS, CHG_HOUR)
The table in this
example is in 1NF and in
2NF. But there is a
transitive dependency
between Bank_Code_No.
and Bank, because
Bank_Code_No. is not
the primary key of this
relation.
To get to the third
normal form (3NF), we
have to put the bank
name in a separate
The table in this
example is in 1NF and in
2NF. But there is a
transitive dependency
between Bank_Code_No.
and Bank, because
Bank_Code_No. is not
the primary key of this
relation.
To get to the third
normal form (3NF), we
have to put the bank
name in a separate