1

Unit 3: Relational Database Design

Unit 3: Relational Database Design

Computer Science Department: University of the People
CS 2203 - Databases 1
Shanthini S
December 5, 2024.
2
Unit 3: Relational Database Design

a. Normalization is a database design technique that organizes data into tables to reduce

redundancy and dependency anomalies. It involves breaking down a large table into

smaller, more focused tables and defining relationships between them.

Normalization includes creating tables and establishing relationships between those

tables according to rules designed both to protect the data and to make the database

more flexible by eliminating two factors: redundancy and inconsistent dependency.

(Vidhya et al. 2016)

Normalization is a very essential technique in database design, outlined below are a few

reasons why it is very essential

 Reduced data redundancy: Normalization reduces the possibility of discrepancies and

conserves storage space by getting rid of redundant data.

 Improves data integrity: By enforcing data dependencies and constraints,

normalization makes sure that data is both accurate and consistent.

 Optimized query performance: It is easier to query well-normalized databases because

the database engine can quickly find and get the data that is needed.

 Enhanced data flexibility: Normalized databases are more adaptive to changes since

individual tables can be modified without impacting the overall database structure.

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

1. 1st Normal Form does not allow multi valued attribute or composite attribute

and their combinations. It states that domain of the attribute includes only

single value, atomic or indivisible value. (Vidhya et al, 2016)

The above schema is already in 1st Normal Form as it contains atomic data,

contains a Primary Key and there are no repeating groups.

3
Unit 3: Relational Database Design

BOOKS
Book_ID (Primary Key)
Title
Author
Genre
Publisher
Publication_Year
ISBN
Price

2. 2nd Normal Form: For this schema to conform to 2NF, we examine the

dependencies, we identify that Title, Author, Genre, Publisher,

Publication_Year, ISB and Price are partially dependent on Book_ID

To conform to 2NF we remove partial dependencies and separate entities with

different characteristics.

To normalize this we decompose the table into :

BOOKS
PUBLISHERS
Book_ID Primary Key
Book_ID Foreign key
Title
Publisher
Genre
Publication_Year
ISBN
Price

Authors
Book_ID Foreign Key
Author_Name
4
Unit 3: Relational Database Design
3. 3NF: to allow our schema to conform to 3NF we remove transitive

dependencies, create independent entities and establish clear relationships.

BOOKS
Book_ID Authors
Primary Key
Book_ID Foreign Key
Title
Author_Name
Genre
ISBN

BOOKPUBLISHERS
PUBLISHERS
Publisher_ID Primary Key
Book_ID
Publisher_Name Foreign Key
Publication_Year
Price

4. To conform to BCNF, we address complex functional dependencies, create a

more granular independent entity. BCNF is a stricter form of 3NF that

addresses a specific type of anomaly.

BOOKS BOOKDETAILS
Book_ID Primary Key Book_ID Primary Key

Title ISBN
Genre Price

BOOKAUTHORS AUTHORS
Book_ID Primary Key Author_ID Primary Key
Author_ID Author_Name
5
Unit 3: Relational Database Design
PUBLISHERS BOOKPUBLISHERS
Publisher_ID Primary Key Book_ID Primary Key
Publisher_Name Publisher_ID
Publication_Year

c. 1NF to 2NF ; we addressed partial dependencies at this stage in that some attributes
were dependent only on a part of the primary key.

2NF to 3NF: at this stage we addressed transitive dependencies, where-in attributes

were dependent on other none-prime attributes.

d. Advantages and potential drawbacks of achieving higher normal forms.

Here are some advantages on Higher Normal forms;

 Higher Normal forms reduce the risks of data inconsistencies and anomalies

 Data is easier to manipulate, as changes in one table does not affect the entire

database.

 Well normalized databases can be queried quite easily, it is easier to modify

the schema.

Outlined below are the drawbacks expected of higher normal forms.

 Higher normal forms can lead to complex database designs with multiple tables.

 Joining multiple tables can sometimes impact query performance especially complex

queries.

 Excessive normalization can lead to potential performance degradation

Reference:

1. Vidhya, V., Jeyaram, G., & Ishwarya, K. (2016). Database management systems. Alpha

Science International.