Normalization
Minimizing redundancy
Fewer problems and less time, minimizing the insertion, deletion and update
Unnormalised form
Without Normalization, it becomes difficult to handle and update the database, without facing
data loss. Insertion, Updating and Deletion
Data in unnormalised form (ONF) is a flat file. It will contain non-atomic data, repeating groups
of data and possibly redundant data. Non-atomic data is where a field contains more than one
item of data.
Atomic??
Atomic is a single value which can not to divide further
First normal form
First normal form states that, the domain of an attribute must include only atomic values.
Data in first normal form (INF) must satisfy the following criteria:
• All fields must contain atomic data
• There must be no repeating groups of data
• There must be a unique key.
Person
Person id First name Second name Phone#
1 Ahmad khan 123,
254,
547
2 hasssan ali 127
Normalization
Attribute
Person_ID First_name Second_name Phone #
Normalization
Phone
Phone id Phone# Person id
1 123 1
2 254 1
3 127 2
Second normal form
A table that is in first normal form (1NF) must meet addition criteria if it to qualify
for second normal form.
Second normal form states that it should meet all the rules for 1NF and there
must be no partial dependence of any of the columns on the primary key
St_ID Batch Name Email Phone Start_d Course Batch Batch faculty
_ID ate _size _time
1 2
2 2
Normalization
St_ID Name Email Phone
1
2
Batch Start_d Course Batch Batch faculty
_ID ate _size _time
2
2
St_ID Batch_ID
1 2
2 2
Normalization
Third normal form
Data in third normal form 3NF must have no non-key dependencies. This means that there
should be no fields that are dependent upon another field that is not a primary key. Therefore
primary keys and compound primary keys can be ignored
faculty_ID Name Dept Dept head
1 ali phy fahad
2 yahya bio ahmad
3 husnain eng ali
faculty_ID Name Dept
1 ali phy
2 yahya bio
3 husnain eng
Dept Dept head
phy fahad
bio ahmad
eng ali
Normalization
Normalization