Scribd
Upload
16 views16 pages

Normalization Module3 Detailed Presentation

Normalization is a method for organizing database tables to reduce redundancy and improve data integrity by eliminating anomalies. It involves several normal forms, each addressing specific issues such as atomic values, partial dependencies, and multivalued dependencies. While normalization enhances structure, it can also introduce complexity, leading to scenarios where denormalization may be preferred for performance reasons.

Uploaded by

M Y LIKHITH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
16 views16 pages

Normalization Module3 Detailed Presentation

Normalization is a method for organizing database tables to reduce redundancy and improve data integrity by eliminating anomalies. It involves several normal forms, each addressing specific issues such as atomic values, partial dependencies, and multivalued dependencies. While normalization enhances structure, it can also introduce complexity, leading to scenarios where denormalization may be preferred for performance reasons.

Uploaded by

M Y LIKHITH
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Introduction to Normalization

• Normalization is a systematic approach of


decomposing tables to eliminate data
redundancy and undesirable characteristics
like insertion, update, and deletion anomalies.

• Real-world Example: In a school database,


storing student info in one table avoids
repeated address data for every subject they
take.
Why Normalize a Database?
• • Avoid data redundancy
• • Improve data integrity
• • Easier to maintain

• Example: An online shopping platform avoids


storing same customer details for every order.
Functional Dependencies
• Functional Dependency means one attribute
uniquely determines another.

• Example: In an employee table, Employee_ID


→ Employee_Name.
• Knowing the Employee_ID, we can determine
the name.
Multivalued Dependencies
• Occurs when an attribute depends on another
attribute independently of other attributes.

• Example: A student can have multiple phone


numbers and multiple email addresses
independently. These must be split into
different tables to avoid data issues.
First Normal Form (1NF)
• Rules:
• • Atomic values (no repeating groups or
arrays)
• • Each field should hold one value only

• Example: Phone numbers split into different


rows instead of storing '12345, 67890' in one
cell.
Second Normal Form (2NF)
• Rules:
• • Must be in 1NF
• • No partial dependency (non-key attribute
should depend on the whole key)

• Example: In a course registration table,


Course_Name should not depend only on
Student_ID.
Third Normal Form (3NF)
• Rules:
• • Must be in 2NF
• • No transitive dependency (non-key → non-
key)

• Example: Student_ID → Dept_ID →


Dept_Name. Dept_Name must go in a
separate table.
Boyce-Codd Normal Form (BCNF)
• Every determinant must be a candidate key.

• Example: If Teacher_Name → Subject but not


every subject is taught by only one teacher,
the table needs redesign.
Fourth Normal Form (4NF)
• No multivalued dependencies.

• Example: A person with multiple hobbies and


multiple languages known. Each pair must be
represented without mixing.
Fifth Normal Form (5NF)
• No join dependency or lossless join.

• Example: An employee assigned to multiple


projects for multiple clients. Splitting data into
three related tables avoids duplication and
inconsistency.
Comparison Table of Normal Forms
• 1NF: Atomic values
• 2NF: No partial dependencies
• 3NF: No transitive dependencies
• BCNF: Every determinant is a candidate key
• 4NF: No multivalued dependencies
• 5NF: No join dependencies
When to Stop Normalizing?
• Normalization improves structure but can lead
to complexity and performance loss.

• Example: In reporting systems,


denormalization is preferred to speed up
queries.
Applications of Normalization
• • Banking: Avoid duplicate customer records
• • Hospitals: Patient and appointment records
• • Education: Course registrations
• • E-commerce: Orders, customers, and
inventory
Summary of Normalization
• • Reduces redundancy
• • Improves data integrity
• • Builds structured and efficient databases
• • Each normal form fixes specific issues
Quiz & Interaction
• 1. What’s the main rule of 1NF?
• 2. Give an example of a multivalued
dependency.
• 3. When would you choose not to normalize?

• Ask your classmates and test your


understanding!
Thank You
• Q&A Session
• Ask doubts or share your examples!

You might also like