Fourth Normal Form (4NF) in DBMS Theory - Step-by-Step Execution

Concept Flow - Fourth Normal Form (4NF)

Start with a relation

↓

Check for multivalued dependencies

Yes↓

Decompose relation into smaller relations

↓

Each smaller relation has no multivalued dependencies

↓

Result: Relation is in 4NF

No↓

Relation already in 4NF

↓

End

Start with a database table, check if it has multivalued dependencies, if yes, split it into smaller tables without such dependencies to achieve 4NF.

Execution Sample

DBMS Theory

Relation: Student_Course_Hobby(Student, Course, Hobby)
Check multivalued dependencies:
Student ->> Course
Student ->> Hobby
Decompose into:
Student_Course(Student, Course)
Student_Hobby(Student, Hobby)

Shows how a relation with multivalued dependencies is split into two relations to satisfy 4NF.

Analysis Table

Step	Action	Check	Result	Next Step
1	Start with relation Student_Course_Hobby	N/A	Relation has multivalued dependencies	Check multivalued dependencies
2	Check if Student ->> Course	Yes	Multivalued dependency found	Check if Student ->> Hobby
3	Check if Student ->> Hobby	Yes	Multivalued dependency found	Decompose relation
4	Decompose into Student_Course and Student_Hobby	N/A	Both relations have no multivalued dependencies	Relation is in 4NF
5	Verify no multivalued dependencies in decomposed relations	No	4NF achieved	End

💡 No multivalued dependencies remain after decomposition, so relation is in 4NF

State Tracker

Relation	Start	After Step 4	Final
Student_Course_Hobby	Student, Course, Hobby	Decomposed into Student_Course and Student_Hobby	Two relations: Student_Course(Student, Course), Student_Hobby(Student, Hobby)

Key Insights - 2 Insights

Why do we need to decompose the relation when multivalued dependencies exist?

Because multivalued dependencies cause redundancy and anomalies; decomposition removes these by separating independent data, as shown in steps 3 and 4 of the execution_table.

How do we know when a relation is in 4NF?

When no multivalued dependencies exist except those that are functional dependencies, as confirmed in step 5 of the execution_table.

Visual Quiz - 3 Questions

According to the execution_table, at which step do we perform the decomposition?

A Step 4

B Step 2

C Step 5

D Step 1

💡 Hint

Look at the 'Action' column in the execution_table where decomposition is mentioned.

What is the state of the relation after Step 4 in variable_tracker?

A Still one relation with multivalued dependencies

B Relation is deleted

C Decomposed into two relations without multivalued dependencies

D Relation has more multivalued dependencies

💡 Hint

Check the 'After Step 4' column in variable_tracker for the relation state.

If the relation had no multivalued dependencies at Step 2, what would happen next?

A Decompose the relation anyway

B Declare relation is already in 4NF and end

C Add more attributes

D Ignore and continue checking

💡 Hint

Refer to the 'Next Step' column in execution_table when no multivalued dependencies are found.

Concept Snapshot

Fourth Normal Form (4NF):
- Deals with multivalued dependencies in a relation.
- If multivalued dependencies exist, decompose relation into smaller ones.
- Each smaller relation should have no multivalued dependencies.
- Achieving 4NF removes redundancy and update anomalies.
- 4NF is stricter than 3NF and BCNF.

Full Transcript

Fourth Normal Form (4NF) is a database normalization stage that removes multivalued dependencies from relations. Starting with a relation, we check if any attribute sets have multivalued dependencies. If yes, we split the relation into smaller relations so that each has no multivalued dependencies. This process reduces redundancy and prevents anomalies. When no multivalued dependencies remain, the relation is in 4NF. For example, a Student_Course_Hobby relation with independent multivalued dependencies on Course and Hobby is decomposed into Student_Course and Student_Hobby relations. This ensures data integrity and efficient storage.