Database Management System

Running head : Database Management System

Database Management System Database case scenario is as follows

Notown Records has decided to store information about musicians who perform on its albums (as well as other company data ) in a database

1 . Each musician that records at Notown has an employee number , a name an address , and a phone number . Poorly paid musicians often share the same address , and no address has more than one phone

2 . For each of its elite musicians , Notown needs to keep track of the number of gold and platinum albums

they had and whether they can lead a band

3 . For each sessional musician , Notown keeps track of their musical genre , the band size they usually play in and whether they can solo

4 . Each instrument used in songs recorded at Notown has a name (e .g guitar , synthesizer , flute ) and a musical key (e .g , C , B-flat , E-flat .5 . Each album recorded on the Notown label has a title , a copyright date , a format (e .g , CD or vinyl , and an album identifier

6 . Each song recorded at Notown has a title and an author and is arranged by an elite musician

7 . An elite musician may arrange several songs , but each song has only one arrangement

8 . Each musician may play several instruments , and a given instrument may be played by several musicians

9 . Each album has a number of songs on it , but no song may appear on more than one album

10 . Each song is performed by one or more musicians , and a musician may perform a number of songs

11 . Each album has exactly one elite musician who acts as its producer An elite musician may produce several albums , of course

Notown administration needs the system to be able to perform the following

regular entry of new albums and new songs

monthly reports on the arrangements by each elite musician

intermittent entry and maintenance of sessional musicians - an average of two such transactions are made per month

reports detailing the number of sessional musicians by genre

monthly reports detailing the songs recorded on a albums produced that month and

The ability to make ad hoc queries , for example , `which musician produced a particular album

In the above scenario the requirement of an Entity Relationship Diagram (ERD ) is clearly depicted and must be done for the following reasons

Mapping of the relations between the real world entities

Taking into account the information storing capacity for fetching the right scenario

To capture and find information for fetching the gross data requirement of the organization and its detail

To store data effectively and generate reports for fetching the scenario of the database

Normalization

Navathe (2003 ) mentions that normalization is a process for fetching the database the following

Free of redundant data and

Elimination of insert , update and delete anomalies from the database

Advantages of Normalization

Prevents redundancy of data in the tables

Avoids any anomaly regarding insertion , update and deletion of data

Disadvantages of Normalization...