Normalization ppt for rdbms

1. RDBMS
NORMILIZATION
NAME: 1.Navpreet singh

2. INTRODUCTION
Definitionofnormalization: Normalization isthe
processoforganizingthedata inadatabase
efficiently.Itinvolvesstructuring arelational
database inaccordancewitha seriesofnormal
formsto reduceredundancyanddependency.
Importanceofnormalization inRDBMS:
Normalization iscrucialformaintainingdata
integrity,optimizingdatabase performance,and
facilitatingefficientdata retrievaland
manipulation.

3. Table of contents
{01} {04}
{02} {05}
{03} {06}
Introduction
Whatit is?
Normal forms
1st normal form
2nd normal form
3rd normal form

4. Table of contents
{07} {10}
{08} {11}
{09} {12}
Boyce-codd
normal form
4th normal form
5th normal form
Pros and cons of
normalization
Practical application
Conclusion

5. What it is?
Definition: Normalization is a method used to designa
relational database schema to minimize redundancy
and dependency,thereby ensuring data integrity and
optimizing database performance.
Objectives:The primary objectives of normalization are
to eliminate anomalies (insertion, deletion, and
update), ensure data consistency, reduce storage
space, and simplifydatabase maintenance.
Development:Normalization was proposedby Edgar F.
Codd in his seminal paper "A Relational Model of Data
for Large Shared Data Banks" in 1970,which laid the
foundation for modern relational database
management systems(RDBMS).

6. Normal forms
•Explanationof normal forms: Normal forms are a series of progressive
steps used to eliminate data redundancy and dependency in a relational
database.
•Each normal form addresses specific types of issues: 1NF deals with
atomicity, 2NF with partial dependencies, 3NF with transitive
dependencies, BCNF with candidate keys, 4NF with multi-valued
dependencies, and 5NF with join dependencies.
•Progression: Normalization typically progresses from first normal
form (1NF) to higher normal forms, each stage further refining the
structure of the database.

7. 1st normal form
Definition:In 1NF, every attribute must have a single value, and each
column in a table must be atomic.
Example: Consider a Student table where each student's
information(e.g., name, age, address)is stored in separate
columns, ensuringatomicity and avoidingmultivalued attributes.

8. 2nd normal form
Definition:In 2NF, the table must be in 1NF, and all non-key
attributes are fully functionally dependenton the primary key.
Example: An Orders table where order details (e.g., product
name, quantity) are moved to a separate table linked by order
ID, ensuringeach non-key attribute is dependenton the
primary key.

9. 3rd normal form
Definition:In 3NF, the table must be in 2NF, and it should eliminate
transitive dependencies,ensuring that no non-key attribute is
dependenton another non-key attribute.
Example: An Employee table where employee data (e.g.,
department) depends only on the primary key (employee ID),
eliminating transitive dependencies.

10. Boyce-Codd Normal Form (BCNF)
Definition: BCNF is a stronger versionof 3NF, where every
determinantis a candidate key, ensuring that there are no non-
trivial functional dependencieson the candidate keys.
Example: A Supplier table where supplier informationis organized
to ensure that each determinant(e.g., supplier ID) uniquely
determines all other attributes.
al form

11. 4th normal form
Definition:4NF deals with multi-valued dependencies,ensuring
that each multi-valued dependency is logically independent of
other dependenciesin the table.
Example: A Sales table where multi-valued dependencies(e.g.,
product attributes) are separated into distinct tables to eliminate
redundancyand dependency.

12. 5th normal form
Definition:5NF addressesjoin dependencies, ensuring
that all join dependenciesare inferred by the primarykey
and are logical consequences of the definitions of the
attributes.
Example: Course and Professor tables where the
relationshipbetween courses and professors is
structured to eliminate join dependenciesand ensure data
integrity.

13. Pros and cons of normalization
Advantages:Reduces data redundancy, enhances data
integrity, improves database performance, simplifies
database maintenance, and facilitates scalability.
Disadvantages:Increases database complexity, may lead to
slower query performance due to the need for joins, and
requires careful analysisand planning during database
design.

14. Practical applications
Real-world scenarios: Normalizationis crucial in various
industries such as banking (for managingcustomer accounts),e-
commerce (for handling product inventory), and healthcare (for
maintainingpatient records).
Impact on system scalability and maintenance: Proper
normalizationensures that the database can scale efficiently as
the volume of data grows and simplifies maintenance tasks such
as updates and modifications.

15. Summary of key points: Normalizationis a fundamental
concept in relational database design aimed at reducing
redundancy,improvingdata integrity, and optimizingdatabase
performance.
Importance of understanding and implementing
normalization:Effective normalizationis essentialfor building
robust and efficient relationaldatabases that can meet the
needs of modern applications.
conclusion