Database Normalization The database normalization process is a critical step in our database management for many reasons. Database normalization helps us:
Avoid database anomalies
Manage functional dependencies of data
Achieve a loosely coupled database model
Avoid redundancies
Avoid bugs
Achieve operational efficiency and performance
1F:
All rows must be unique (no duplicate values)
Each cell must contain a single value
Each value should be non divisible (atomic, can’t be split)
2F:
Database must be in 1F
Non partial dependency-All non-prime attributes should be functionally dependent on the candidate key.
3F: Database must be in 2F.
Making sure there are no transitive dependencies in the data. This means we need to ensure no other attribute (beyond the key identifiers or ID columns) can uniquely determine an attribute’s output