Conceptual design, pg.135#13 (pg.122#12, 6th edition)



























Logical design, pg.227#3 (pg.203#3, 6th edition)

a.                3NF

b.               3NF

c.                2NF

CLASS (Course_No, Section_No, Room)

ROOM (Room, Capacity)

d.               1NF

COURSE (Course_No, Course_Name)

CLASS (Course_No, Section_No, Room)

ROOM (Room, Capacity)




Physical design, pg.279#5 (pg.250#6, 6th edition)

A listing of employee schedules showing the employee’s name and the department’s manager.  Rather than joining three tables (SCHEDULE, DEPARTMENT, and EMPLOYEE) to extract data for the list, it may be advisable to combine attributes from these tables giving DeNormalizedSchedule (Department_ID, Employee_ID, Date, Mangager_ID, Employee_Name). This approach is advantageous if such a list is needed frequently.




Data administration, pg.542#2 (pg.488#2, 6th edition)

a.      Aborted transaction. Use rollback.

b.     Database destruction. Use roll forward from the backup copy of the database. If backup copy is not available, use restore/rerun to reprocess the day's transactions (up to the point of failure) against the backup copy of the database).  If the system is mirrored, a switch is also appropriate.

c.      System failure. Same as (b).

d.     Incorrect Data. Enter compensating transaction and notify the student of the error.

If the system is mirrored, it may be possible to switch to the mirrored data and rebuild the corrupted data on a new disk. If the system is not mirrored, it may not be possible to restart because status information in main memory has been lost or damaged. The safest approach is to restart from the most recent checkpoint before the system failure. Since no database change log is created the database cannot be rolled forward by applying after-images. Transactions have to be reprocessed manually.