The task of a database designer is to structure the data in
a way that eliminates unnecessary duplication and provides a
rapid search path to all necessary information. The process
of refining tables, keys, columns, and relationships to
create an efficient database is called normalization

because there is no redundant, neglected data and normalized
tables produce rapid, efficient joins.

There are 5 different normalization methods.

 First Normal Form (1NF): Each field in a table must contain
different information.

 Second Normal Form (2NF): All attributes that are not
dependent upon the primary key in a database table must be
eliminated.

 Third Normal Form (3NF): No duplicate information is
permitted. So, for example, if two tables both require a
common field, this common field information should be
separated into a different table.

 There are 2 more normalization forms, fourth normal form
(4NF) and fifth normal form (5NF), but they are rarely used.
Normalization makes databases more efficient and easier to
maintain.

Normalization:
        Normalization is the process of designing a data
model to efficiently store data in a database. The end
result is that redundant data is eliminated, and only data
related to the attribute is stored within the table.

First normal form (1NF):
	An entity type is in 1NF when it contains no repeating
groups of data.

Second normal form (2NF):
	An entity type is in 2NF when it is in 1NF and when all of
its non-key attributes are fully dependent on its primary key. 

Third normal form (3NF):
	An entity type is in 3NF when it is in 2NF and when all of
its attributes are directly dependent on the primary key.