Normalization in DBMS

Normalization is one of the most important DBMS topics for exams, viva, and technical interviews. Interviewers ask this topic very often because it shows whether you understand clean database design.

What is Normalization?

Normalization is the process of organizing database tables to reduce redundancy and avoid anomalies.

Main goals:

• reduce repeated data
• improve consistency
• avoid update problems
• create better table structure

What are anomalies?

Anomalies are problems caused by poor table design.

Main types:

• insert anomaly
• update anomaly
• delete anomaly

What is Functional Dependency?

Functional dependency means one attribute depends on another.

If A -> B, it means the value of A determines the value of B.

Functional dependency is important because normalization rules are based on dependencies.

First Normal Form (1NF)

A table is in 1NF if:

• all values are atomic
• no repeating groups exist

Example

If one student row contains multiple phone numbers in one column, it is not in 1NF.

To convert to 1NF, each field should contain only one value.

Second Normal Form (2NF)

A table is in 2NF if:

• it is already in 1NF
• every non-key attribute depends on the whole primary key

2NF mainly removes partial dependency.

Example

If a composite key is (student_id, course_id) and student_name depends only on student_id, then that is partial dependency and should be separated.

Third Normal Form (3NF)

A table is in 3NF if:

• it is already in 2NF
• no non-key attribute depends on another non-key attribute

3NF removes transitive dependency.

Example

If student_id -> dept_id and dept_id -> dept_name, then dept_name should not stay in the same table as a non-key dependent attribute.

BCNF

BCNF stands for Boyce-Codd Normal Form.

A table is in BCNF if:

• for every dependency A -> B, A must be a candidate key

BCNF is stronger than 3NF.

Why normalization matters

Normalization helps by:

• reducing duplication
• making updates easier
• improving data consistency
• creating cleaner schema design

Is normalization always enough?

Normalization improves design, but too much normalization can sometimes increase joins and reduce read performance. In some systems, denormalization is used carefully for speed.

Interview-style answer

Normalization is the process of organizing data to reduce redundancy and avoid anomalies. 1NF removes repeating groups, 2NF removes partial dependency, 3NF removes transitive dependency, and BCNF is a stronger form where every determinant must be a candidate key.

Quick Revision Points

• 1NF = atomic values
• 2NF = remove partial dependency
• 3NF = remove transitive dependency
• BCNF = determinant should be candidate key
• normalization improves consistency

Viva Questions

1. What is normalization?
2. Why is normalization needed?
3. What is 1NF?
4. What is the difference between 2NF and 3NF?
5. What is BCNF?
6. What are insert, update, and delete anomalies?

Final Tip

In exams and interviews, always explain normalization with one simple dependency example. It makes the concept much easier to understand and remember.