Scribd
Upload
22 views

Database Journal Unit 3

Uploaded by

madandolataiwo
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
22 views

Database Journal Unit 3

Uploaded by

madandolataiwo
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Normalization is a critical process in database design that ensures data consistency, reduces

redundancy, and improves scalability (Elmasri & Navathe, 2016). It involves transforming
relations into higher normal forms to eliminate data anomalies and dependencies.

Why Normalization is Essential

Normalization is vital for database design because it:

Reduces Data Redundancy


Data redundancy occurs when duplicate data exists in multiple locations. Normalization
eliminates redundancy, reducing storage requirements and minimizing data inconsistencies
(Codd, 1970).

Eliminates Data Inconsistencies


Data inconsistencies arise when duplicate data is updated differently. Normalization ensures data
consistency by eliminating redundancy and ensuring data integrity (Elmasri & Navathe, 2016).

Improves Data Scalability


Normalization enables databases to scale efficiently by reducing data redundancy and improving
data organization (Kroenke & Auer, 2018).

Enhances Query Performance


Normalization optimizes query performance by reducing the amount of data to be processed and
improving data retrieval efficiency (Date, 2003).

Supports Data Integrity Constraints


Normalization ensures data integrity by enforcing constraints, such as primary keys and foreign
keys, to maintain data consistency (Elmasri & Navathe, 2016).

Normalizing the Library Database Relation


The unnormalized relation:

Books (Book_ID, Title, Author, Genre, Publisher, Publication_Year, ISBN, Price)

First Normal Form (1NF)


Divide the relation into two tables to eliminate repeating groups:

Book
(Book_ID, Title, Genre, Publisher, Publication_Year, ISBN, Price)

Book_Author
(Book_ID, Author)

Second Normal Form (2NF)


Eliminate partial dependencies:

Book
(Book_ID, Title, Genre, Publisher, Publication_Year, ISBN, Price)

Book_Author
(Book_ID, Author)

Author
(Author_ID, Author_Name)

Third Normal Form (3NF)


Eliminate transitive dependencies:

Book
(Book_ID, Title, Genre, Publisher_ID, Publication_Year, ISBN, Price)
Publisher
(Publisher_ID, Publisher_Name)

Book_Author
(Book_ID, Author_ID)

Author
(Author_ID, Author_Name)

Boyce-Codd Normal Form (BCNF)

Ensure that each determinant is a candidate key:

Book
(Book_ID, Title, Genre, Publisher_ID, Publication_Year, ISBN, Price)

Publisher
(Publisher_ID, Publisher_Name)

Book_Author
(Book_ID, Author_ID)

Author
(Author_ID, Author_Name)

Functional Dependencies and Normalization


Functional dependencies describe the relationships between attributes.

First Normal Form (1NF)


Book_ID → Title, Genre, Publisher, Publication_Year, ISBN, Price; Author → Book_ID

Second Normal Form (2NF)


Book_ID → Title, Genre, Publisher, Publication_Year, ISBN, Price; Book_ID, Author →
Author_Name

Third Normal Form (3NF)


Book_ID → Title, Genre, Publisher_ID, Publication_Year, ISBN, Price; Publisher_ID →
Publisher_Name; Book_ID, Author_ID → Author_Name

Boyce-Codd Normal Form (BCNF)


Book_ID → Title, Genre, Publisher_ID, Publication_Year, ISBN, Price; Publisher_ID →
Publisher_Name; Book_ID, Author_ID → Author_Name

Advantages and Drawbacks of Higher Normal Forms


Higher normal forms offer several advantages.

Advantages
Improved Data Integrity
Higher normal forms eliminate data redundancy and inconsistencies.

Reduced Data Redundancy


Higher normal forms minimize storage requirements.

Enhanced Query Performance


Higher normal forms optimize query performance.

Better Scalability
Higher normal forms enable databases to scale efficiently.

Drawbacks
Increased Complexity
Higher normal forms introduce complexity.

More Joins Required


Higher normal forms require more joins.

Potential Performance Overhead


Higher normal forms may introduce performance overhead.

Conclusion
Normalization is essential for database design, ensuring data integrity, scalability, and query
efficiency.

References:
- Codd, E. F. (1970). A relational model of data for large shared data banks. Communications of
the ACM, 13(6), 377-387.
- Date, C. J. (2003). An introduction to database systems. Addison-Wesley.
- Elmasri, R., & Navathe, S. B. (2016). Fundamentals of database systems. Pearson Education.
- Kroenke, D. M., & Auer, D. J. (2018). Database concepts. Pearson Education.

You might also like