Ch6 Slides - Normalisation of Database Tables Pt. 1 (2019)

Chapter 6
Normalisation of Database
Tables (Part 1)
CMT221/CMM222
Database Organisation and Design
Teh Je Sen (2019) 1

Learning Objectives
Normalisation and its role in database design

The various normal forms and how to transform them
Teh Je Sen (2019) 2

Re-cap Quiz
Let’s first re-cap what we learned last week!
Teh Je Sen (2019) 3

Normalisation
Evaluate and correct tables to

minimise data redundancies and
reduce data anomalies
Stages
First normal form (1NF)
Second normal form (2NF)
Third normal form (3NF)
Teh Je Sen (2019) 4

Normalisation
Generally, higher normal forms are better than lower

normal forms
3NF is sufficient for most business database needs
Teh Je Sen (2019) 5

Denormalisation
Produces a lower normal form

Higher redundancy but may lead to
increased performance
Performance Redundancy
Teh Je Sen (2019) 6

Redundancies and Anomalies
Identify redundancies of the following table
How do we fix it?

Teh Je Sen (2019) 7
No repetition!
How is this better?

Teh Je Sen (2019) 8
Redundancy leads to anomalies

What anomalies can you remember?
Insertion
Deletion
Modification
Teh Je Sen (2019) 9

Insertion Anomaly
How will insertion anomaly occur for the following

unnormalised table?
Teh Je Sen (2019) 10

Insertion Anomaly
If new staff member is inserted, correct details of the

branch has to be entered

Insertion Anomaly
Cannot enter information for a new branch without

creating a null staff info.

Insertion Anomaly
How will deletion anomaly occur for the following

unnormalised table?

Insertion Anomaly
What happens if we delete the record for Art Peters or

Sally Stern??

Insertion Anomaly
We lose all information for branch B003 and B004

Insertion Anomaly
How will update anomaly occur for the following

unnormalised table?

Insertion Anomaly
If branch information is changed, all records of staff

located at that branch needs to be updated.

Importance of Normalisation
Produce a set of tables with desirable properties

(avoid anomalies)
Support the requirements of a user or company

Example – Need for Normalisation
Assume there’s a company called Bob Ltd. that

manages building projects
It charges its clients by billing hours spent by each
employee on each project
The hourly billing rate depends on the employee’s
position

Based on this table, Bob can generate a report


The original table seems to be sufficient because it

can generate a report to bill the client
But what potential problems can you identify from
the table?
Let’s look at it again

NULL
NULL
NULL
NULL
There are many null values for the primary key

NULL
NULL
NULL
NULL
Update anomaly
NULL
NULL
NULL
NULL
JOB_CLASS can lead to inconsistencies during data entry

E.g. Database Designer, DB Designer, DD Designer
NULL
NULL
NULL
NULL
Other anomalies such as insertion and deletion

Normalisation
So what do you think are the characteristics of a

normalised table?
Each table represents a single subject

All nonprime attributes are dependent only on the
primary key
No anomalies

How do we normalise?
Work with one table at a time

Identify undesirable dependencies
Break down the table into new tables to remove
dependencies
Ensure that all tables are at least in 3NF

Recap: Functional Dependency
What is functional dependency?

What does it mean when we say
attribute B is functionally dependent on attribute A?
Attribute A determines exactly one value of attribute
B
What examples can you give me?

In the following functional dependence, which

attribute is the determinant and which one is the
dependent?
STU_NUM  (STU_LNAME, STU_FNAME)

In the following functional dependence, which

attribute is the determinant and which one is the
dependent?
STU_NUM  (STU_LNAME, STU_FNAME)

Recap: Full Functional Dependency
Is the following functional dependency a fully

functional dependency?
(STU_NUM, STU_LNAME)STU_GPA

No, because STU_LNAME is not required to

uniquely identify STU_GPA
(STU_NUM, STU_LNAME)STU_GPA

A full functional dependence refers to a functional

dependency where the entire collection of attributes
in the determinant is required for the relationship

Other Dependencies
Time to learn two new types of dependencies that will

be addressed by normalisation
Partial dependency
Transitive dependency

Partial Dependency
A functional dependence whereby the determinant is

only part of the primary key
Identify the partial dependencies for the example in
the following slide

Partial Dependency
(STUD_NUM, COURSE_NUM)
(STUD_NAME ,COURSE_NAME, GPA)
How about GPA?

Partial Dependency
(STUD_NAME ,COURSE_NAME, GPA)
STUD_NAME and COURSE_NUM are both

dependent on only part of the primary key
GPA is fully dependent on the entire primary key
Transitive Dependency
A functional dependence whereby the determinant is

a nonkey attribute
In other words, an attribute functionally depends on
another nonkey attribute
Identify the transitive dependencies for the example
in the following slide

Partial Dependency
(STUD_NAME, COURSE_NAME, HOSTEL_NUM,
HOSTEL_NAME)
HOSTEL_NAME is dependent on HOSTEL_NUM,

which is a nonkey attribute
Example
Take out a piece of paper

For all exercises, write down the solutions

Example
Identify the partial dependencies in this table

(use the dependency notation XXYY)
STU_ID PROJ_ID STU_NAME PROJ_NAME HOURS
1001 9221 Bob Plane 2
1002 9222 Eve Boat 3
1001 9223 Bob Car 5
STUD_IDSTU_NAME
PROJ_IDPROJ_NAME

Example
Identify the transitive dependencies in this table

(use the dependency notation XXYY)
STU_ID STU_NAME POSTCODE CITY
1001 Bob 11700 Gelugor
1002 Eve 11900 Bayan Lepas
1003 Wan 11000 Balik Pulau
POSTCODECITY

Example
Identify the partial and transitive dependencies in this

table (E – Employee, J – Job)
E_ID J_ID E_NAME E_AGE J_SALARY J_TITLE DEPT_ID DEPT_NAME
001 A001 Bob 26 1000 Manager B001 Sales
002 A002 Eve 21 2500 Clerk B001 Sales
003 A003 Clare 25 1000 Manager B002 IT
E_ID(E_NAME, E_AGE, DEPT_ID)

J_ID(J_SALARY, J_TITLE)
DEPT_IDDEPT_NAME
J_TITLEJ_SALARY
Normalisation Process

First Normal Form (1NF)
Steps:
Eliminate repeating groups
Identify primary key
Identify all dependencies

Repeating Groups
A group of multiple entries of the same or multiple

types can exist for any single key attribute
occurrence
One primary key value determines multiple entries

Normalising to 1NF
Step 1:
Eliminate repeating groups by ensuring that each
record is complete

Normalising to 1NF

Normalising to 1NF

Normalising to 1NF
Step 2:
Identify a primary key that can uniquely identify
each record
What would be a suitable primary key for the table?

Normalising to 1NF
Why do we need a composite key?

Normalising to 1NF
Step 3:
Identify all dependencies
Depict all dependencies using a dependency
diagram

How do we draw a dependency diagram?
Steps:
List out all attribute names in a row
Draw arrows to indicate all functional dependencies
A B C D

Transitive
Identify the dependencies Dependency
Functional Dependency
Partial
Dependency

Transitive
Draw the dependency diagram Dependency
Partial
Dependency

1NF Dependency Diagram

Draw the dependency diagram
No partial dependency Transitive dependency
staffNo name position salary branchNo branchAdd telNo
How about positionsalary?

Alternative Solution
Partial dependency
staffNo name position salary branchNo branchAdd telNo
Functional Dependency Transitive dependency

Last one!

001 A001 Bob 26 1000 Manager B001 Sales
002 A002 Eve 21 2500 Clerk B001 Sales
003 A003 Clare 25 1000 Manager B002 IT
004 A004 Adam 23 2500 Clerk B002 IT
Partial dependency Transitive dependency Transitive dependency
Why can J_TITLE determine J_SALARY?

Teh Je Sen (2019)
60
Second Normal Form (2NF)
Table is already in 1NF

and has no partial dependencies
How do you eliminate partial dependencies?

Eliminating Partial Dependencies
Let’s take a look at the following table.

What are the partial dependencies?
How do you think we can eliminate them?
1001 9221 Bob Plane 2
1002 9222 Eve Boat 3
1001 9223 Bob Car 5

Steps:
Create a new table for each partial dependency
Remove dependent attributes from the main table
and put them into the new tables
Draw the normalised versions of the following tables!
1001 9221 Bob Plane 2
1002 9222 Eve Boat 3
1001 9223 Bob Car 5

STU_ID STU_NAME PROJ_ID PROJ_NAME

1001 Bob 9221 Plane
1002 Eve 9222 Boat
1001 Bob 9223 Car
STU_ID PROJ_ID HOURS

1001 9221 2
1002 9222 3
1001 9223 5
Is every table in 2NF?

Exercise 1
Convert the following dependency diagram into 2NF
A B C D E F G H

Solution 1
Ensure each table is in 2NF!
A B C F
C D E
B G H

Exercise 2
Convert the following dependency diagram into 2NF

Solution 2
Name change to reflect

Teh Je Sen (2019) table name 68
2NF Summary
A table is in 2NF if it is
1NF
Has no partial dependencies

Third Normal Form (3NF)
Table is already in 2NF

and has no transitive dependencies
How do you eliminate transitive dependencies?

Make new tables
Use the determinant as primary key
Reassign corresponding dependent attributes

Which tables are already in 3NF?
Transitive
dependency

Normalising to 3NF
How do we normalise this table?
Create new table with the nonkey determinant(s) as

primary key
Reassign the corresponding dependent(s) into the
new table

Solution

3NF Summary
A table is in 3NF if it is
2NF
Has no transitive dependencies

Practice
Normalise the following dependency diagram to be

3NF
A B C D E F G

Solution
All tables are in 3NF
A B F
A E F G
B C E D

Practice 2
Convert the following ERD into a dependency

diagram that is at least 3NF
APPOINTMENT
PK App_Num
DOCTOR
FK1 Doc_EmpID
PK Doc_EmpID
App_Date
Doc_Fname
App_PatientID
Doc_Lname
App_P_Name
Doc_CellPhone
App_Postcode
App_City

Solution
Draw a dependency diagram for each table

Identify their dependencies and normal forms
App_
App_Num Doc_EmpID App_Date App_PatientID App_P_Name App_Postcode
City
2NF
Doc_EMPID Doc_Fname Doc_Lname Doc_CellPhone
3NF

Solution
There are no partial dependencies
App_
City
2NF

Solution
Remove transitive dependencies
App_
City
2NF

Solution
App_Num Doc_EmpID App_Date PatientID
3NF
PatientID P_Name Postcode City
2NF

Solution
App_Num Doc_EmpID App_Date PatientID
3NF
PatientID P_Name Postcode
3NF
Postcode City
3NF
Higher Normal Forms
3NF is sufficient for business transactional databases

But there are also higher-level normal forms:
Boyce-Codd Normal Form (BCNF)
Fourth Normal Form (4NF)

BCNF
Every determinant is a candidate key

If there is a determinant that is not a candidate key,
the table is not in BCNF
If a table only has only one candidate key, BCNF is
equivalent to 3NF

4NF
A table that is 3NF

And also has no multivalued dependency

Ch6 Slides - Normalisation of Database Tables Pt. 1 (2019)

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ch6 Slides - Normalisation of Database Tables Pt. 1 (2019)

Uploaded by

Copyright:

Available Formats

Chapter 6

Teh Je Sen (2019) 1

Normalisation and its role in database design

Teh Je Sen (2019) 2

Let’s first re-cap what we learned last week!

Teh Je Sen (2019) 3

Evaluate and correct tables to

Teh Je Sen (2019) 4

Generally, higher normal forms are better than lower

Teh Je Sen (2019) 5

Produces a lower normal form

Teh Je Sen (2019) 6

Identify redundancies of the following table

How do we fix it?

How is this better?

Redundancy leads to anomalies

Teh Je Sen (2019) 9

How will insertion anomaly occur for the following

Teh Je Sen (2019) 10

If new staff member is inserted, correct details of the

Teh Je Sen (2019) 11

Cannot enter information for a new branch without

Teh Je Sen (2019) 12

How will deletion anomaly occur for the following

Teh Je Sen (2019) 13

What happens if we delete the record for Art Peters or

Teh Je Sen (2019) 14

We lose all information for branch B003 and B004

Teh Je Sen (2019) 15

How will update anomaly occur for the following

Teh Je Sen (2019) 16

If branch information is changed, all records of staff

Teh Je Sen (2019) 17

Produce a set of tables with desirable properties

Teh Je Sen (2019) 18

Assume there’s a company called Bob Ltd. that

Teh Je Sen (2019) 19

Based on this table, Bob can generate a report

Teh Je Sen (2019) 21

The original table seems to be sufficient because it

Teh Je Sen (2019) 22

There are many null values for the primary key

JOB_CLASS can lead to inconsistencies during data entry

Other anomalies such as insertion and deletion

So what do you think are the characteristics of a

Each table represents a single subject

Teh Je Sen (2019) 27

Work with one table at a time

Teh Je Sen (2019) 28

What is functional dependency?

Teh Je Sen (2019) 29

In the following functional dependence, which

Teh Je Sen (2019) 30

In the following functional dependence, which

Teh Je Sen (2019) 31

Is the following functional dependency a fully

Teh Je Sen (2019) 32

No, because STU_LNAME is not required to

Teh Je Sen (2019) 33

A full functional dependence refers to a functional

Teh Je Sen (2019) 34

Time to learn two new types of dependencies that will

Teh Je Sen (2019) 35