The assignment is focused on a database that serves as a music repository with the following table entities: Artist, Album, Song, Playlist.

Each table entity can have multiple entries, and will have a numeric primary key (or a composite primary key), a descriptive (or name) attribute, possibly an attribute pointing to another table, and at least one other field of your choice.

Each artist can have one or more albums. Each album can have one or more songs. Each playlist can have zero or more songs.

You'll set-up your database in MySQL.

Following are the submittals for the assignment.

a) Submit the SQL statements to create the table entities, including primary keys, foreign keys, and constraints.

b) Explain a table example where your database is initially not normalized and what you would do to normalize it to an acceptable level.

c) Submit a series of SQL statements that you can you use to add a song to a playlist as a transaction that's committed.

d) How could you use a SQL stored procedure to add a song to a playlist at a specific position (you might need to add an additional attribute for sequence to the playlist table)? Along with the explanation, submit the SQL statements to create the stored procedure, with a portion of the logic.

e) What specific change would you make to allow setting random or sequential play at the individual playlist level. Include the SQL statements used to alter the impacted table(s) or summarize the steps within MySQL to modify the table(s).

f) Imagine the database is available to multiple users with just one user able to add to or modify the data. What database security approach could you use?

g) Briefly describe how aspects of this database solution fits into the Database Life Cycle levels. Include a pointed example for each level (e.g. for the Maintenance and Evolution level a possible upgrade).

h) Submit a screenshot of your schema entry with the tables under it from MySQL.

i) EXTRA CHALLENGE: Research how you would add actual song files to your database.