Normalization DBMS (NDCS10/02)

STEPS ON NORMALIZATION

Before Normalization

1. Begin with the list of all the fields that must appear in the database
2. Do not include computed field
3. Identify the field that can be the primary key
4. Example :
Sales Orders (SalesOrderNo, Date, CustomerNo, CustomerName,
CustomerAdd, ClerkNO, ClerkName, {ItemNo, Description, Qty, UnitPrice})

Normalization First Normal Form (1NF)

1. Separate repeating group into the new table

What is repeating group?
Fields that maybe repeated several time for one documents/ entity.
2. Create a new table containing the repeating data
3. The primary key of the new table (repeating group) is always composite.
Eg : item number .
4. Bring the original table PK into the new table for the linking of data
purposes.
5. Example :
The new table:
Sales Order Details (SalesOrderNo, ItemNo, Description, Qty, UnitPrice)
Original table:
Sales Orders (SalesOrderNo, Date, CustomerNo, CustomerName,
CustomerAdd, ClerkNO, ClerkName)

Normalization Second Normal Form (2NF)

1. Remove Partial Dependencies

What are partial dependencies?
A type of functional dependencies where an attribute is functionally
dependent on only part of the primary key (PK must be a composite key)
2. Create separate table with the functional dependent data and the part
of the key on which it depends. Tables created at this step will usually
contain description of resources

By : Ms. Jelciana Page 1

 Normalization DBMS (NDCS10/02)

3. Example :
From the new table above, looks at the attribute that partial dependency
to the primary key. All the fields except the primary key will be removed
from original table. The primary key will be left in the original table to allow
linking of data. So, the new table as below:
Inventory Items (ItemNo, Description)
Original tables:
Sales Order Details (SalesOrderNo, ItemNo, Qty, UnitPrice)
Sales Orders (SalesOrderNo, Date, CustomerNo, CustomerName,
CustomerAdd, ClerkNO, ClerkName)

Normalization Third Normal Form (3NF)

1. Remove Transitive Dependencies

What are transitive dependencies?
A type of the functional dependency where an attribute is functionally
depend on the attribute other than the primary key
2. Create a separate table containing the attribute and the fields that are
functional dependent on it. Table created at this step usually contain the
descriptions of either the resources or agent. Keep the copy of the key
attribute in the original file.
3. Example:
From the above original table, identify the attribute with the transitive
dependencies.
Sales Orders (SalesOrderNo, Date, CustomerNo, CustomerName,
CustomerAdd, ClerkNO, ClerkName)
So the new tables:
Customers (CustomerNo, CustomerName, CustomerAdd)
Clerks (ClerkNo, ClerkName)
Original table:
Inventory Items (ItemNo, Description)
Sales Order ((SalesOrderNo, Date, CustomerNo, ClerkNO)
Sales Order Details (SalesOrderNo, ItemNo, Qty, UnitPrice)

By : Ms. Jelciana Page 2