Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

I need help Normalizing a database to where there are no duplicates like in the

ID: 3832134 • Letter: I

Question

I need help Normalizing a database to where there are no duplicates like in the BandMember Table 'Guitar' 'Bass' etc. appears more than once or the type of genre in the Songs. Is this OK or no? If so what needs to be done to fix it?

Here is the ER Diagram:

And here are the populated tables:

Musician Table

BandMember Table

Band Table

Instructor Table

Performance Table

Song Table

Band Member Musician bandMemID INT musicianID INT instrument VARCHAR (45) firstName VARCHAR(45) musicianID INT lastName VARCHAR(45) band ID INT o gender VARCHAR(2) ------tea birthday DATE Indexes experience VARCHAR(45) PRIMARY Indexes fk and Member Musician id PRIMARY fk BandMember Band idx Band band ID INT band Name VARCHAR (45) totalMembers INT instrutorID INT Indexes PRIMARY fk Band Instructor1 idx Instructor instrudonID INT ame VARCHAR 45) lastName VARCHAR(45) gender VARCHAR(2) o specialty VARCHAR(45) Indexes PRIMARY Performance v time (0) date DATE Song ID INT t bandID INT Indexes fk Performance Song1 idx PRIMARY fk Performance Bandi idx Song song ID INT title VARCHAR(45) genre VARCHAR (45) Indexes PRIMARY

Explanation / Answer

This is absolutely fine. There are no transitive dependencies present so no need of creating a separate table for such repetitive values as it will serve no purpose than increasing the processing overhead through joins.

Hire Me For All Your Tutoring Needs
Integrity-first tutoring: clear explanations, guidance, and feedback.
Drop an Email at
drjack9650@gmail.com
Chat Now And Get Quote