Database Management System (DBMS) / Normalization in DBMS

Anomalies due to redundant data

When data is not properly normalized, redundant data (duplicate or repetitive information) can lead to serious data anomalies. These are inconsistencies or errors during basic operations like insert, update, or delete.


🚨 Types of Anomalies Caused by Redundant Data

📝 Update Anomaly

Occurs when updating redundant data in one place but not everywhere it appears.

Example:

A student's course instructor name is stored in every row. If the instructor changes, you must update it in every row.

If you miss some, data becomes inconsistent.

StudentID

Name

Course

Instructor

101

Alice

Math

Dr. Sharma

102

Bob

Math

Dr. Sharma

  • If Dr. Sharma changes to Dr. Mehta, and you forget to update in one row — Update Anomaly.


🚫 Insert Anomaly

Occurs when you cannot insert data into the table without other unrelated data.

Example:

You want to add a new course, but you don’t yet have a student enrolled in it.

StudentID

Name

Course

Instructor

(null)

(null)

Statistics

Dr. Rao

  • Inserting nulls just to record a course? That's an Insert Anomaly.


❌ Delete Anomaly

Occurs when deleting one piece of data also deletes important related data unintentionally.

Example:

If a student is the only one enrolled in a course and you delete their record, the course and instructor info is lost too.

StudentID

Name

Course

Instructor

105

Zara

Music

Dr. Bose

  • If Zara drops out and her row is deleted, info about Music course and Dr. Bose is gone — Delete Anomaly.


🔁 Why Does Redundancy Cause These?

Redundancy means storing the same data repeatedly, often in the same table. This:

  • Increases dependency of unrelated data on each other

  • Makes data inconsistent across rows

  • Creates integrity problems


✅ Solution: Normalization

Breaking large redundant tables into smaller related ones removes duplication, and avoids these anomalies.


🧾 Summary Table

🧨 Anomaly

❓ What Happens

😱 Due to...

Update

Change made in one place, not everywhere

Repeated data in many rows

Insert

Can’t add data without other data

Unnecessary dependency

Delete

Deleting data removes valuable info

Data stored together unnecessarily