The Normalization Occurs The Problem In Data Redundancies Where We Have The Problem
Of Data Anomalies?
-> Then, Data Anomalies Can Be Have Different Types Like Insertion, Updation and
Deletion etc.
-> So, we have to complete such operation efficiently while doing any one
completly otherwise it generates an mis-guided or redundant data.
***** 1NF*****
-> In the first normal form we eliminate the problem of atomicity.
-> So, it finds the table which contains a group of data not allowed for this
normal form, where it creates seprate tables for each related tables.
-> And then it defines primary key for each of the table.
***** 2NF ******
-> The first rule is that the data is must be in 1NF.
-> Second is the data doesn't contains the partial dependency, means only the non-
key column within table has must a single identifiable key only.
-> So, if we have composite primary key, then we need to decompose it first by
seprating the data in different tables.
**** 3NF ***** (No Transitive Dependency)
-> In this it ensures that their is no duplicated data and also ensures the
referencial integrity, which is essential for that.
-> For, that it's necessary that the data is must be in 2NF, and we can easily
understand that the non-key column not depend upon other non-key columns.
-> For example, C is Depends Upon B (C -> B) and also B is depends upon A (B -> A)
then here we can see that the C is transitively depends upon the "A" (C -> A).
which is not allowed by this 3rd normal form.
***** BCNF ****** (No Functional Dependency)
-> Necessary to be in the 3rd NF.
-> Then here we have (A -> B) Then "A" is a super key here, means more than one
column that can identify each row uniquely from table.
-> So, in this BCNF we have to create separate table if there is a functional
dependencies.
-> Means there is no non-key attribute is related to the non-prime which is a
super key then we can seprate such dependencies.
