database mgnt Essay

733 Words Oct 8th, 2013 3 Pages
Given the file structure shown in Figure P1.1, answer Problems 1 - 4.

FIGURE P1.1 The File Structure for Problems 1-4

1. How many records does the file contain? How many fields are there per record?
There are 5 filds, each with 7 records

2. What problem would you encounter if you wanted to produce a listing by city? How would you solve this problem by altering the file structure? Some of the project managers are mentioned several times, that would cause duplication in the city database.

3. If you wanted to produce a listing of the file contents by last name, area code, city, state, or zip code, how would you alter the file structure?

Divide address capabilities, by dividing MANAGER_ADDRESS into its component parts
…show more content…
Looking at the EMP_NAME and EMP_PHONE contents in Figure P1.5, what change(s) would you recommend? That is, break up the data componnts whenever possible. example, separate the EMP_NAME into EMP_FNAME, EMP_INITIAL, and EMP_LNAME. This will make it easier to organize employee data. Also EMP_PHONE data should be split up into EMP_AREACODE and EMP_PHONE. For example, breaking up the phone number into the area code 653 and the phone number 234-3245.

7. Identify the various data sources in the file you examined in Problem 5.

Employee data such as names and phone numbers.
Project data such as project names.
Job data such as the job charge per hour. If you start with an EMPLOYEE file, the job charge per hour does not belong in that file
The project hours, which are the hours worked by the employee for that project.

8. Given your answer to Problem 7, what new files should you create to help eliminate the data redundancies found in the file shown in Figure P1.5?

Data redundancy can be controlled by storing the data in separate tables. Each of these tables would be named to indicate its contents, i.e., we would recommend the creation of four tables named PROJECT, EMPLOYEE, JOB, and CHARGE,

9. Identify and discuss the serious data redundancy problems exhibited by the file structure shown in Figure P1.9. (The file is meant to be used as a

Related Documents