Database Normal Forms – Summary
Introduction
Normalization is a systematic process used in relational database design to reduce redundancy and
improve data integrity. It organizes tables and relationships in a database according to a set of rules
called normal forms. Each normal form addresses a specific type of redundancy or anomaly that
can occur during data storage and manipulation.
Why Normalization?
Normalization helps prevent insertion anomalies, deletion anomalies, and update anomalies. It
ensures that each piece of information is stored in only one place, making databases easier to
maintain and less prone to inconsistencies.
First Normal Form (1NF)
A relation is in First Normal Form if all attributes contain atomic (indivisible) values and each record
can be uniquely identified. This means that there are no repeating groups or multi■valued
attributes.
Key rules of 1NF: • Each column contains atomic values. • Each record must be unique. •
Repeating groups are removed and placed into separate rows.
Second Normal Form (2NF)
A relation is in Second Normal Form if it satisfies the requirements of First Normal Form and all
non-key attributes are fully functionally dependent on the entire primary key.
Key idea:
2NF eliminates partial dependency. A partial dependency occurs when a non-key attribute depends
on only part of a composite primary key rather than the whole key.
Example concept:
If a table has a composite key (StudentID, CourseID) and an attribute StudentName depends only
on StudentID, then StudentName should be moved to another table. This removes the partial
dependency.
Benefits of 2NF:
• Reduces redundancy caused by partial dependencies. • Improves consistency of stored data. •
Makes updates and inserts safer.
Third Normal Form (3NF)
A relation is in Third Normal Form if it is in Second Normal Form and has no transitive
dependencies. A transitive dependency occurs when a non-key attribute depends on another
non-key attribute.
Example:
If a table contains (StudentID, DepartmentID, DepartmentName) where DepartmentName depends
on DepartmentID, then DepartmentName should be placed in a separate Department table.
Boyce-Codd Normal Form (BCNF)
BCNF is a stricter version of Third Normal Form. A relation is in BCNF if, for every functional
dependency X → Y, X is a superkey. In other words, every determinant must be a candidate key.
Purpose of BCNF:
BCNF resolves certain anomalies that 3NF may still allow when multiple candidate keys exist in a
relation.
Fourth and Fifth Normal Forms
Fourth Normal Form (4NF)
A relation is in Fourth Normal Form if it is in BCNF and contains no multi-valued dependencies. This
means that independent multi-valued facts about an entity must be stored in separate tables.
Fifth Normal Form (5NF)
Fifth Normal Form, also known as Project-Join Normal Form (PJNF), ensures that tables cannot be
decomposed further without losing information. It deals with join dependencies that arise when
reconstructing data from smaller tables.
Summary of Normal Forms
1NF – Atomic attributes and no repeating groups. 2NF – No partial dependencies on a composite
key. 3NF – No transitive dependencies. BCNF – Every determinant must be a candidate key. 4NF –
No multi-valued dependencies. 5NF – No join dependencies requiring further decomposition.
Normalization is essential in database design because it ensures efficient storage, minimizes
redundancy, and improves data consistency. In practice, most databases are normalized up to
Third Normal Form or BCNF depending on the system requirements.