Normalization or the database normalization is a process to organize the data into database tables. To make a good database design, you have to follow Normalization practices. Without normalization, a database system might be slow, inefficient, and might not produce the expected result. Normalization reduces data redundancy and inconsistent data dependency.
To make a good database design, you must know the normal forms and their best uses. In this article, we will discuss the normal forms.
Normal Forms: Types of Normalization
The worlds' database community has developed a certain guideline for ensuring that the databases in our application should be normalized in a specific way. These are referred to as normal forms and are numbered from one where the lowest form of normalization is referred to as the first normal form or 1NF through five which is the fifth normal form or 5NF along with the BCNF which is the Boyce Code Normal Form. While working with the real-time application or scenarios, we will often see different forms of the normalization such as 1NF, 2NF, and 3NF, along with the occasional 4NF and BCNF. but the fifth normal form (5NF) is very rarely seen and used in the enterprise application due to its complexity.
We organize the data into database tables by using normal forms of rules or conditions. Normal forms help us to make a good database design. Generally, we organize the data up to the third normal form. We rarely use the fourth and fifth normal forms.
To understand normal forms consider the following unnormalized database table. Now we will normalize the data in the below table using normal forms.
First Normal Form (1NF)
A database table is said to be in 1NF if it contains no repeating fields/columns. The process of converting the UNF table into 1NF is as follows:
Separate the repeating fields into new database tables along with the key from the unnormalized database table.
The primary key of new database tables may be a composite key
1NF of the above UNF table is as follows:
Second Normal Form (2NF)
A database table is said to be in 2NF if it is in 1NF and contains only those fields/columns that are functionally dependent(means the value of the field is determined by the value of another field(s)) on the primary key. In 2NF we remove the partial dependencies of any non-key field.The process of converting the database table into 2NF is as follows:
Remove the partial dependencies(A type of functional dependency where a field is only functionally dependent on the part of the primary key) of any non-key field.
If field B depends on field A and vice versa. Also for a given value of B, we have only one possible value of A and vice versa, Then we put the field B into a new database table where B will be the primary key and also marked as a foreign key in a parent table.
2NF of the above 1NF tables is as follows:
As you can see in the above example, We have divided our 1NF table into two tables viz. Table 1 and Table2. Where Table 1 contains project information. and Table 2 contains information on the employee assigned to the specific projects.
We have introduced a new column called project_code which is the primary key for table 1. Records can be uniquely identified in Table 1 using the project id column itself.
Third Normal Form (3NF)
A database table is said to be in 3NF if it is in 2NF and all non-keys fields should be dependent on the primary key We can also say a table to be in 3NF if it is in 2NF and no fields of the table are transitively functionally dependent on the primary key. The process of converting the table into 3NF is as follows:
Remove the transitive dependencies(A type of functional dependency where a field is functionally dependent on the Field that is not the primary key. Hence its value is determined, indirectly by the primary key )
Make a separate table for transitive dependent Fields.
3NF of the above 2NF tables is as follows:
Boyce Code Normal Form (BCNF)
A database table is said to be in BCNF if it is in 3NF and contains each and every determinant is a candidate key. The process of converting the table into BCNF is as follows:
Remove the nontrivial functional dependency.
Make a separate table for the determinants.
BCNF of the below table is as follows:
Fourth Normal Form (4NF)
A database table is said to be in 4NF if it is in BCNF and the primary key has a one-to-one relationship to all non-keys fields We can also say a table to be in 4NF if it is in BCNF and contains no multi-valued dependencies. The process of converting the table into 4NF is as follows:
Remove the multivalued dependency.
Make a separate table for multivalued Fields.
4NF of the below table is as follows:
Fifth Normal Form (5NF)
A database table is said to be in 5NF if it is in 4NF and contains no redundant values or We can also say a table to be in 5NF if it is in 4NF and contains no join dependencies. The process of converting the table into 5NF is as follows:
Remove the join dependency.
Break the database table into smaller and smaller tables to remove all data redundancy.
5NF of the below table is as follows:
Database designing is one of the critical tasks for the successful implementation of a database management system of the application that meets the data requirements of an enterprise application to be developed. Doing database normalization in DBMS is a crucial process that helps to create concrete database systems that are cost-effective while having better security models attached to them. The complete functional database dependencies are a very important component of the normalized data process
In this article, I try to explain the Normalization with an example. I hope after reading this article you will be able to understand Normal Forms. I would like to have feedback from my blog readers. Please post your feedback, question, or comments about this article.