Recap exercise

Consider the data-model for the spotify dataset

  • The dataset has some inherint issues with data duplication as it is only 1 table

  • Also issues are present within the current modelling of genre

How can decomposition be used to normalize the data and enchance the data-quality?

Implement your changes

We would like to change the datamodel in the following ways:

  • Users are now considered an entity with attributes decided by you

  • Users can have playlists and songs can be placed within playlists

    • What are the relationships between the new entities?

  • Implement constraints such as: Primary Key, Foreign Key, On Update/Delete & Check - if necessary

Implement the solution in the DDL script and reverse engineer with an EER diagram

Hand in:

https://kea-fronter.itslearning.com/LearningToolElement/ViewLearningToolElement.aspx?LearningToolElementId=1187047

PreviousIndexing, views & normalisationNextFirebase configuration

Last updated