Scribd
Upload
21 views

Chapter 5: Database Normalization

The document discusses database normalization. It describes several normal forms including 1NF, 2NF, 3NF, and 4NF. It defines key concepts like functional dependence, primary keys, foreign keys, and update anomalies. Normalization aims to eliminate anomalies by decomposing tables and only linking entities through their primary and foreign keys. This improves data integrity and avoids data redundancy.

Uploaded by

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

Chapter 5: Database Normalization

The document discusses database normalization. It describes several normal forms including 1NF, 2NF, 3NF, and 4NF. It defines key concepts like functional dependence, primary keys, foreign keys, and update anomalies. Normalization aims to eliminate anomalies by decomposing tables and only linking entities through their primary and foreign keys. This improves data integrity and avoids data redundancy.

Uploaded by

David Dave Fua
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 31

hapter 5 : Database Normalizatio

Normalization Process
Identify the existence of potential problems,
known as the update anomalies
Tables must be types of normal forms:
FIRST NORMAL FORM (1NF)
SECOND NORMAL FORM (2NF)
THIRD NORMAL FORM (3NF)
FOURTH NORMAL FORM (4NF)
FUNCTIONAL DEPENDENCE
KEYS

FUNCTIONAL
DEPENDENCE
A column is FUNCTIONALLY DEPENDENT on another
column when each value in the second column is
associated with exactly one value in the first column.

Think Premier products


Rep Table
Is Last Name functionally dependent on RepNum?

Customer Table
Is CustomerName functionally dependent on
RepNum?

OrderLine Table
Is Quoted price functionally dependent on
OrderNum?

KEYS
A column is PRIMARY KEY if:
All columns in the table are functionally dependent on that
column
If its concatenated key, no other concatenation of fields or
single field would fulfill the same purpose.

Is Class the Primary Key for Part Table?

Is CustomerNum the primary key for the


Customer Table?

Is the combination of OrderNum and the PartNum the


primary key for the OrderLine table?

Is the combination of PartNum and the Description the


primary key for the Part Table?

?
S
Y
E
K
E
T
A
D
I
D
N
A
C
E
R
A
T
A
H
W

FIRST NORMAL FORM (1NF)

SECOND NORMAL FORM


(2NF)

A column is a Nonkey Column if:


- the column is not part of the primary key
E.g.:

UPDATE ANOMALIES
UPDATE
INCONSISTENT DATA
ADDITIONS
DELETIONS

DEPENDENCY DIAGRAM

THIRD NORMAL FORM (3NF)


A table is in third normal form when it is in normal
form and only DETERMINANTS it contained are
candidate keys
Determinant is any column(s) that determines
another column

Example of a
Determinant:

Customers
First and Last
Names are
determined
by the
RepNum
See RepNum
20

Incorrect Decomposition
Data Redundancy
Always link the Primary Key to the Foreign Key not the
Dependant Data
E.g.: Link the CustomerNum to the RepNum not
First/LastName
Lets See Figure 5.13 and 5.14

FOURTH NORMAL FORM(4NF)


It is in fourth normal form if:
It is in third normal form
There are no MULTIVALUED DEPENDENCIES

Multivalued Dependencies
When the data in the first column is related
to data in the second column AND is related
to data in the third column BUT its
relationship to the data in third column is
independent of its relationship in the second
column

PROBLEMS:
1.Update
Problems
2.Addition/Deletio
n Problems

You might also like