Course contentsShow
← Software Engineering
Lesson 861 of 1,93327. Database Design in PracticeFree lesson

The Normal Forms (1NF, 2NF, 3NF)

Understand the first three normal forms and the rules for achieving each level of normalization.

The Normal Forms (1NF, 2NF, 3NF)

You'll learn the first three normal forms and the specific rules that define each level of normalization.

Now that you understand what normalization is, let's explore the formal levels that guide how we structure our tables. Each "normal form" is a checkpoint that ensures your database meets increasingly strict quality standards.

First Normal Form (1NF)

Rule: Every column must contain atomic (indivisible) values, and each row must be unique.

Think of a recipe card: instead of listing "flour, sugar, eggs" in one ingredient field, you'd have one ingredient per line. No lists, no repeating groups.

Violates 1NF: A Student table with a PhoneNumbers column containing "555-1234, 555-5678"

Achieves 1NF: Separate rows for each phone number, or a separate StudentPhones table.

Second Normal Form (2NF)

Rule: Must be in 1NF, AND every non-key column must depend on the entire primary key (no partial dependencies).

This only matters when you have a composite key (multiple columns forming the key). Every piece of data should relate to the whole key, not just part of it.

Violates 2NF: A table with key (StudentID, CourseID) but also storing StudentName (depends only on StudentID, not the full key).

Achieves 2NF: Move StudentName to a separate Students table.

Third Normal Form (3NF)

Rule: Must be in 2NF, AND no non-key column depends on another non-key column (no transitive dependencies).

Every fact should depend directly on the key, not on other regular columns.

Violates 3NF: Storing both ZipCode and City in a customer table, where City depends on ZipCode rather than CustomerID.

Achieves 3NF: Create a separate ZipCodes table linking zip codes to cities.

Key Takeaway: 1NF eliminates repeating groups, 2NF removes partial key dependencies, and 3NF removes dependencies between non-key columns—each level builds on the previous one to reduce redundancy and anomalies.