Database normalization is a database schema design technique, by which an existing schema is modified to minimize redundancy and dependency of data.
Normalization split a large table into smaller tables and define relationships between them to increases the clarity in organizing data.
Some facts about database normalization
- The words normalisation and normal form refers to the structure of database.
- Normalization was developed by IBM researcher E.F. Codd In the 1970s.
- Normalization increases the clarity in organizing data in Database.
Normalization of a Database is achieved by following a set of rules called ‘forms’ in creating the database.
There are 5 rules mentioned below.
1st Normal Form (1NF)
Each column is unique.
Employee table following 1NF:
2nd Normal Form (2NF)
The entity should be considered already in 1NF and all attributes within the entity should depend solely on the unique identifier of the entity.
Product table following 2NF:
Products Category table:
Products Brand table:
3rd Normal Form (3NF)
The entity should be considered already in 2NF and no column entry should be dependent on any other entry (value) other than the key for the table.
If such an entity exists, move it outside into a new table.
3NF is achieved are considered as the database is normalized.
Boyce & Codd (BCNF)
3NF and all tables in the database should be only one primary key.
Tables cannot have multi-valued dependencies on a Primary Key.
Composite key shouldn’t have any cyclic dependencies.
Well this is a highly simplified explanation for Database Normalization. One can study this process extensively though. After working with databases for some time you’ll automatically create Normalized databases. As, it’s logical and practical.