• Here's where we left off. We realized that having all three entities in one table led to update, insert and delete anomalies.

  • We recognized the problem: three entities in one table — but threw out the bad schema and started over with the E/R model.

  • Now we will examine a different approach, based on improving a bad schema.

  • Artist info is obviously (highly) redundant.

  • This is because of a one-to-many relationship between Artist and Album.

  • Separate the Album columns into their own table.