Why Normalization?

• To develop a logical data model for relational

database systems in order to create an
accurate representation of the data, its
relationships, and constraints.
Normalization
• Normalization is a method for organizing
data elements in a database into tables.

1 2

Normalization Avoids… Normalization Stages…

• Duplication of Data – The same data is listed in multiple
lines of the database Normalization is a three stage process:
• Insert Anomaly – A record about an entity cannot be
inserted into the table without first inserting • After the first stage, the data is said to be
information about another entity – Cannot enter a in first normal form (1NF)
customer without a sales order
• Delete Anomaly – A record cannot be deleted without • After the second, it is in second normal
deleting a record about a related entity. Cannot delete a
sales order without deleting all of the customer’s form (2NF)
information.
• Update Anomaly – Cannot update information without
• After the third, it is in third normal
changing information in many places. To update form (3NF)
customer information, it must be updated for each sales
order the customer has placed
3 4

1
 Before Normalization Before Normalization – Example
1. Begin with a list of all the fields that must
appear in the database. Think of this as one
big table.
2. Do not include computed fields
3. One place to begin getting this information
is from a printed document used by the
system.
4. Additional attributes besides those for the
entities described on the document can be Fields in the original data table will be as follows (Think of this as the baseline – one large table)
SalesOrderNo, Date, CustomerNo, CustomerName, CustomerAdd, ClerkNo, ClerkName,
added to the database. ItemNo, Description, Qty, UnitPrice
5 6

Normalization: First Normal Form (1NF) First Normal Form Example

• The new table is as follows:
• Separate Repeating Groups into New Tables.
SalesOrderNo, ItemNo, Description, Qty, UnitPrice
• Repeating Groups Fields that may be repeated
several times for one document/entity • The repeating fields will be removed from the
• Create a new table containing the repeating data original data table, leaving the following:
• The primary key of the new table (repeating SalesOrderNo, Date, CustomerNo, CustomerName,
group) is always a composite key; usually CustomerAdd, ClerkNo, ClerkName
document number and a field uniquely
describing the repeating line, like an item • These two tables are a database in first normal
number. form (1NF)

7 8

2
 First Normal Form (1NF) QA Normalization: Second Normal Form (2NF)
Questions: What if we did not normalize the • Remove Partial Dependencies.
Database to First Normal Form? • Functional Dependency: The value of one attribute
in a table is determined entirely by the value of
Answer: Repetition of Data – So, Header data another.
(customer no., customer name, customer • Partial Dependency: A type of functional dependency
address, etc) is repeated for every line in where an attribute is functionally dependent on only
sales order. part of the primary key (primary key must be a
composite key).
• Create separate table with the functionally
dependent data and the part of the key on which it
depends. Tables created at this step will usually
contain descriptions of resources.
9 10

Second Normal Form Example Second Normal Form (2NF) QA

• The new table will contain the following fields:
Question: What if we did not normalize the Database to
ItemNo, Description Second Normal Form?
• All of these fields except the primary key will be Answer:
removed from the original table. The primary key will 1. Repetition of Data – Description would appear every
be left in the original table to allow linking of data: time we had an order for the item
SalesOrderNo, ItemNo, Qty, UnitPrice 2. Delete Anomalies – All information about inventory
• Never treat price as dependent on item. Price may be items is stored in the SalesOrderDetail table. Delete a
sales order, delete the item.
different for different sales orders (discounts, special
customers, etc.) 3. Insert Anomalies – To insert an inventory item, must
insert sales order.
• Along with the unchanged table below, these tables 4. Update Anomalies – To change the description, must
make up a database in second normal form: change it on every SO.
SalesOrderNo, Date, CustomerNo, CustomerName,
CustomerAdd, ClerkNo, ClerkName 11 12

3
Normalization: Third Normal Form (3NF) Third Normal Form Example
• The new tables would be:
• Remove transitive dependencies.
CustomerNo, CustomerName, CustomerAdd
• Transitive Dependency: A type of functional
ClerkNo, ClerkName
dependency where an attribute is functionally
dependent on an attribute other than the primary • All of these fields except the primary key will be
removed from the original table. The primary key
key. Thus its value is only indirectly determined by will be left in the original table to allow linking of
the primary key. data as follows:
• Create a separate table containing the attribute and SalesOrderNo, Date, CustomerNo, ClerkNo
the fields that are functionally dependent on it. • Together with the unchanged tables below, these
Tables created at this step will usually contain tables make up the database in third normal form.
descriptions of either resources or agents. Keep a ItemNo, Description
copy of the key attribute in the original file. SalesOrderNo, ItemNo, Qty, UnitPrice

13 14

Third Normal Form (3NF) QA Completed Tables in Third Normal Form

Question: What if we did not normalize the Database to Customers: CustomerNo, CustomerName, CustomerAdd
Third Normal Form?
Answer:
Clerks: ClerkNo, ClerkName
• Repetition of Data – Detail for Cust/Clerk would
appear on every SO
• Delete Anomalies – Delete a sales order, delete the Inventory Items: ItemNo, Description
customer/clerk
• Insert Anomalies – To insert a customer/clerk, must Sales Orders: SalesOrderNo, Date, CustomerNo, ClerkNo
insert sales order.
• Update Anomalies – To change the name/address, etc,
must change it on every SO. SalesOrderDetail: SalesOrderNo, ItemNo, Qty, UnitPrice

15 16

4
Exercise: Normalize …

17