Scribd
Upload
71 views3 pages

Normalization Case Study 1

The document discusses normalizing a database related to books, authors, and royalties into third normal form. It includes the dependencies between attributes and describes the process of converting the relations from first normal form to second normal form by eliminating partial dependencies, and then from second normal form to third normal form by eliminating transitive dependencies.

Uploaded by

s11146134
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
71 views3 pages

Normalization Case Study 1

The document discusses normalizing a database related to books, authors, and royalties into third normal form. It includes the dependencies between attributes and describes the process of converting the relations from first normal form to second normal form by eliminating partial dependencies, and then from second normal form to third normal form by eliminating transitive dependencies.

Uploaded by

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

The dependency diagram in the figure below indicates that authors are

paid royalties for each book that they write for a publisher. The amount of
the royalty can vary by author, by book, and by edition of the book.

1. Based on the dependency diagram, create a database whose tables are at least in 2NF,
showing the dependency diagram for each table.

a. Identify dependencies

Desirable dependency (i.e., dependency based on the PK):


ISBN, Author_Num -> BookTitle, LastName, Publisher, Royalty, Edition

Partial dependency:
ISBN -> BookTitle, Publisher, Edition
Author_Num -> LastName

Transitive dependency:
BookTitle -> Publisher

b. Check if the table is in 1NF


 All key attributes are defined
 There are no repeating groups in the table
 All attributes are dependent on the primary key

c. Convert to 2NF
Step 1: Make new tables to eliminate partial dependencies
i. For each PK component that acts as a determinant in a partial dependency,
create a new table with a copy of that component as the PK.
ii. Remain these PK component in the original table
 Serve as FKs for the relationship needed to relate the new tables to
the original table.
. Step 2: Reassign corresponding dependent attributes
i. Attributes that are dependent in a partial dependency
 removed from the original table
 placed in the new table with the dependency’s determinant
ii. Attributes that are not dependent in a partial dependency will remain in the
original table

The 2NF normalization results (in 1NF, no partial dependencies):

2. Create a database whose tables are at least in 3NF, showing the dependency diagram for each
table.

Convert the 2NF to 3NF:

Step 1: Make new tables to eliminate transitive dependencies


 Determinant: Any attribute whose value determines other values within a row
 Determinant remain in the original table to serve as a FK

Step 2: Reassign corresponding dependent attributes


 Identify the attributes that are dependent on each determinant identified in Step 1.
 Place the dependent attributes in the new tables with their determinants and
remove them from their original tables.

Step 3: Check all of the tables to make sure that each table has a determinant and that no
table contains inappropriate dependencies
The 3NF normalization results (in 2NF, no transitive dependencies):

You might also like