Scribd
Upload
54 views

Itec 65 - Advanced Database Management System Normalization

The document discusses database normalization. It defines 1NF, 2NF, and 3NF. 1NF requires a primary key and eliminating repeating groups. 2NF eliminates partial dependencies by ensuring non-key columns depend on the whole composite key. 3NF removes transitive dependencies by placing attributes in separate tables if they depend on other non-key attributes rather than the primary key. Various examples of normalized and un-normalized tables are provided to illustrate the normalization forms.

Uploaded by

Sohfia Jesse Vergara
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
54 views

Itec 65 - Advanced Database Management System Normalization

The document discusses database normalization. It defines 1NF, 2NF, and 3NF. 1NF requires a primary key and eliminating repeating groups. 2NF eliminates partial dependencies by ensuring non-key columns depend on the whole composite key. 3NF removes transitive dependencies by placing attributes in separate tables if they depend on other non-key attributes rather than the primary key. Various examples of normalized and un-normalized tables are provided to illustrate the normalization forms.

Uploaded by

Sohfia Jesse Vergara
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

ITEC 65 - ADVANCED DATABASE MANAGEMENT SYSTEM

Normalization

Usually involves dividing large table into smaller (less redundant) tables and defining
relationships between them.
Develop by E.F. Codd in 1972.

1NF

Vocabulary
Primary Key – unique identifier
Non-Key Attributes – children of the primary key
Determinant – attribute to find out values assigned to other attributes in the same row
Dependent – look to the primary key for reference

Determinant Dependents
b,c -> A
Primary Key A Non-Key b Non-Key c
Unique Attribute A Attribute b Attribute c
Unique Attribute A Attribute b Attribute c

Requirements
 Identify a unique primary key
 Have just one set of values per column
 Have just one set values per cell
 Eliminate repeating data

Hints
-in almost all cases when a table is normalized, it is broken into more than one table
-it is very important to identify the relationships between the parent and child tables

1nf Common Errors

cust_id First_Name Order cust_id First_Name Order


1 John 600 1 John 600,638,2025
1 John 638 4 Ribbon 675,518
1 John 2025
4 Ribbon 675
4 Ribbon 518
ITEC 65 - ADVANCED DATABASE MANAGEMENT SYSTEM

Un-Normalize

EmployeeID First_Name Last_Name AssignmentID BeginDate


101 Jef Hinkle 2 2011-01-15
4 2011-01-16
6 2011-01-17

Normalize
AssignmentID EmployeeID First_Name Last_Name BeginDate
2 101 Jef Hinkle 2011-01-15
4 101 Jef Hinkle 2011-01-16
6 101 Jef Hinkle 2011-01-17

Another Example
ClientRental

clientNo cName propertyNo pAddress rentStart rentFinish rent ownerNo oName


cr76 John PG4 Address1 2012-01-01 2012-12-31 350 CO40 Tina
PG16 Address2 2012-01-01 2012-12-31 450 CO93 Tony
cr56 Aline PG4 Address1 2013-01-01 2013-12-31 350 CO40 Tina
PG36 Address3 2013-01-01 2013-12-31 375 CO93 Tony
PG16 Address2 2013-01-01 2013-12-31 450 CO93 Tony

Draw Here
ITEC 65 - ADVANCED DATABASE MANAGEMENT SYSTEM

2NF

Vocabulary
Composite Key – made of > 1 column
Partial Dependency – non-key that depends on part of the Composite Key

Composite Key Dependents


e->A whereas c,d -> AB
Primary Key A Primary Key B Non-Key c Non-Key d Non-Key e
Determinant A Determinant B Attribute c Attribute d Attribute e
Determinant A Determinant B Attribute c Attribute d Attribute e

Requirements
 Is in 1NF
 Eliminate Partial Dependency
 Non-Key columns must depend on all keys of the composite key

Hints
-If the Primary Key is made up of a single column, it is guaranteed to be in 2NF
-If a non-key column is related to just one of the columns in the composite key, it partially depends on
the whole key and needs to be in separate table.

Draw Here
ITEC 65 - ADVANCED DATABASE MANAGEMENT SYSTEM

3NF

Vocabulary
Composite Primary Key – made of > 1 column
Transitive Relationship – non-key is dependent to another non-key

Composite Key Dependents


e->d whereas c,d -> AB
Primary Key A Primary Key B Non-Key c Non-Key d Non-Key e
Determinant A Determinant B Attribute c Attribute d Attribute e
Determinant A Determinant B Attribute c Attribute d Attribute e

Requirements
 Is in 1NF
 Is in 2NF
 Eliminate transitive dependencies

Hints
-If a non-key attribute directly depends on another non-key attribute, then there is a transitive
dependency
-If attributes do not contribute to a description of the key, remove them to a separate table

Draw Here

Summary

You might also like