IST $210-$ Normalized Music Database

Required Screenshots

Provide screenshot$($s$)$ of the SQL statements used to create the new tables

Provide screenshot$($g$)$ of the SQL statements used to create the new tables $2.$ Provide screenshot$($s$)$ of the SQL statements used to establish referential integrity

Provide screenshot$($s$)$ of a successful import log for each table. $3.$

Total Screenshots: $3$

Introduction $-$ In order to complete this lab, we will be using the database created in Lab $2$ to

create a new, normalized, set of tables. The following is an ER Diagram showing the content of

our music database, presently there is only one table:

In this lab we want our database to have the normalized version of the data in our music$\_$basic

table. This will help reduce data redundancy and increase data integrity. At the end of this lab

you will end up with four new tables $($five tables overall including the original music$\_$basic

table$).$ Our new tables will contain very similar data as we have seen in music$\_$basic. Your music

database at the end of this lab should look like the following ER Diagram:

Provide screenshot$($s$)$ of the SQL statements used to establish referential interuity between

the appropriate tables

a$.$ Make sure to use CASCADE UPDATE and CASCADE DELETE

b$.$ Hint: You con interpret which columns are foreign keys from the ERD

c$.$ If you completed this step in #$1,$ you do not need to provide additional screenshots.

Part $2$: In order to complete part $2$ of the lab, you will need to ensure that you have the

following files. You will need to populate the tables using the import wizard in the workbench

with the below files. A successful important will wield the listed amount rows in each table.

genre.csv $-11$ rows

artist.csv $-19$ rows

alburn.csv $-22$ rows

Instructions:

You will need to interpret this diagram and complete the following steps to create our new

tables and populate them with data.

Hints:

You can use the CSV files located on Canvas to help you create the tables

All the tables have an ID column, sometimes referenced in a different table. This is the

primary key$-$foreign key relationship.

If foreign key constraints exist, the order you create tables and import data matters.

You might want to start with the ortists table.

Include all screenshots in a single Word document with headers for each step.

Part $1$: Our new normalized database contains $4$ tables. You will need to create the new tables

using SQL statements and establish referential integrity between the appropriate tables.

Provide screenshot $($s$)$ of the SQL statements used to create the new tables $($include the

statement and the Action Output$)$