You are on page 1of 5

NORMALIZATION

Normalization is a systematic approach of decomposing tables to


eliminate data redundancy(repetition) and undesirable characteristics like
Insertion, Update and Deletion Anomalies. It is a multi-step process that
puts data into tabular form, removing duplicated data from the relation
tables.
Example:
In the mentioned Data Table of College Students where Branch, HOD
Name and Office_telephone No is repeated which occupies extra Space
and creates a problem in updating Data. Hence, leads to Data Redundancy.
The Data Redundancy can be minimised by Normalizing the Data.

DATA
REDUNDANCY

This issue
can be
resolved by
creating
different
table for Student and Branch Name .

NORMALIZATION can be done in following ways –


1.) 1NF 2.)2NF 3.) 3NF

We uses 1st Normal Form to create scalable table which can be easily
extended.
NORMALIZATION

3 basic Rules of 1 NF-

1.)Each Column should contain atomic (Single) values.


2.)A column should contain values of same type.
3.)Each column should have unique name.

Doesn’t have atomic


value in Column
Doesn’t have atomic values
in column

Table in 1 NF

2 NF (2nd Normal Form)


Second Normal Form (2NF) is based on the concept of full functional
dependency. Second Normal Form applies to relations with composite keys,
that is, relations with a primary key composed of two or more attributes.
A relation that is not in 2NF may suffer from the update anomalies.
To be in second normal form
1.)A relation must be in first normal form(1st Normal Form) .
2.) A relation must not contain any partial dependency.

Consider the example given below.


NORMALIZATION
STUD_N COURSE_N
O O COURSE_FEE
     
1 C1 1000
2 C2 1500
1 C4 2000
4 C3 1000
4 C1 1000
2 C5 2000

Here,
COURSE_FEE cannot alone decide the value of COURSE_NO or STUD_NO;
COURSE_FEE together with STUD_NO cannot decide the value of
COURSE_NO;
COURSE_FEE together with COURSE_NO cannot decide the value of
STUD_NO;
Hence,
COURSE_FEE would be a non-prime attribute, as it does not belong to the
one only candidate key {STUD_NO, COURSE_NO} ;

To convert the above relation to 2NF,


we need to split the table into two tables such as :
Table 1: STUD_NO, COURSE_NO
Table 2: COURSE_NO, COURSE_FEE

STUD_N COURSE_N COURSE_FE


O COURSE_NO   O E
         
1 C1   C1 1000
2 C2   C2 1500
1 C4   C4 2000
4 C3   C3 1000
4 C1   C1 1000
2 C5   C5 2000

3 NF (3rd Normal Form)


NORMALIZATION
A relation is in third normal form, if –
1.)A relation must be in first normal form (1st Normal Form).
2.)There should be no transitive dependency for non-prime
attributes.
A relation is in 3NF if at least one of the following conditions holds in every
non-trivial function dependency( X –> Y):

 If A->B and B->C are two Dependencies, then A->C is called transitive dependency.
The Normalization of 2NF relations to 3NF involves the removal of transitive
dependencies. If a transitive dependency exists, we remove the transitively
dependent attribute(s) from the relation by placing the attribute(s) in a new relation
along with a copy of the determinant.

Consider the examples given below.


STUDENT TABLE:

For this relation in table , STUD_NO -> STUD_STATE and STUD_STATE ->
STUD_COUNTRY are true. So STUD_COUNTRY is transitively dependent on
STUD_NO. It violates the third normal form. To convert it in third normal
form, we will decompose the relation STUDENT (STUD_No, STUD_NAME,
STUD_STATE, STUD_COUNTRY_STUD_AGE) as:
STUDENT(STUD_No,STUD_NAME,STUD_STATE,STUD_COUNTRY_STUD_AG
E)
STATE_COUNTRY(STATE,COUNTRY)
NORMALIZATION

You might also like