Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gurjit
Starting Member
7 Posts |
 Posted - 2011-04-05 : 12:32:36
|
Hi Frens,i'm creating a songs database, for that i've 3 tables as listed below1) Albums2) Artists3) Songsif you look at the below Database Diagram, do you think it's right or would you suggest improvements, thanks |
|
|
denis_the_thief
Aged Yak Warrior
596 Posts |
Posted - 2011-04-06 : 14:13:55
|
| Looks pretty good.You could have a table Song_Artists:Song_ArtistIDSongIDArtistIDfor cases when tou have more than 2 singers on the song, but that could be overkill. |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2011-04-06 : 23:54:12
|
| Song to Artist is a many-to-many relationship, so you need a SongArtist table to implement that.Song to Album is a many-to-many relationship, so you need a SongAlbum table to implement that. Obviously an album has many songs, but a song can be on many albums.You could also break Song into the Song itself, and performances of that song which would be what goes on an album and has Artists. The song could have a many to many relationship with Writers.CODO ERGO SUM |
|
|
|
|
|
|
3 tables normalization design suggestions req.