Course contentsShow
← Computer Science
Lesson 1642 of 2,87237. Database Design and NormalizationFree lesson

Fourth Normal Form (4NF) Overview

Understanding multi-valued dependencies and 4NF requirements for eliminating independent multi-valued facts.

Fourth Normal Form (4NF) Overview

What you'll learn: How to eliminate redundancy caused by multiple independent multi-valued facts stored in the same table.

Beyond BCNF

You've already mastered BCNF, which handles functional dependencies. But there's another subtle anomaly lurking: multi-valued dependencies (MVDs). Fourth Normal Form (4NF) addresses situations where a table stores two or more independent sets of multi-valued facts about an entity, creating unnecessary redundancy.

What is a Multi-Valued Dependency?

A multi-valued dependency exists when one attribute determines a set of values for another attribute, independent of other attributes. Think of it like this: imagine an Instructor table tracking both the courses a professor can teach and their phone numbers:

Instructor_ID | Course     | Phone
101           | Databases  | 555-1234
101           | Databases  | 555-5678
101           | Networking | 555-1234
101           | Networking | 555-5678

The problem? Courses and phone numbers are independent facts about the instructor. Every course must be paired with every phone number, creating a cross-product effect and massive redundancy.

4NF Requirements

A table is in Fourth Normal Form if:

  1. It is already in BCNF
  2. It has no non-trivial multi-valued dependencies

To achieve 4NF, decompose the table into separate relations, each storing one multi-valued fact:

Instructor_Courses          Instructor_Phones
Instructor_ID | Course      Instructor_ID | Phone
101           | Databases   101           | 555-1234
101           | Networking  101           | 555-5678

Now you can add courses or phone numbers independently without duplication.

When Does 4NF Matter?

If a table naturally represents multiple independent many-to-many relationships from the same entity, you're likely violating 4NF and should split it.

Key Takeaway: Fourth Normal Form eliminates redundancy from independent multi-valued dependencies by separating each multi-valued fact into its own table, preventing unnecessary data duplication and update anomalies.