New York University _ NYU Tandon School of Engineering _ CS-GY 6083 - B, Spring-2020. Principles of Database Systems. Final Exam.

CS-GY 6083 - B, Spring-2020. Principles of Database Systems. A) Answer following questions briefly [20 points] i) Which RAID Level schemes will you choose for the storage of Data Files and Redo Log Files and why? Which type of storage media will you choose for storing database backups and why? ii) What are two major goals for handling database transactions? Explain how these goals are being managed in database. iii) Explain difference between UNDO and REDO operations with examples. iv) Explain characteristics of Shared Locks and Exclusive locks. B) Draw ERD (relational model) for following problem set [20 points] Consider Creative Art Network (CAN) with following entities and attributes. ARTIST (aID, Name, DateOfBirth, Email, Phone, zipcode) MUSEUM (iID, item_title, item_size{height, width, weight}, item_status) GALLARY (gID, gallery_name, gallery_address) SHOW (sID, start_date, end_date) CAN is an art museum which owns a very large volume of art work, created by one or multiple artists. At any point in time, a work of art is either on display at the museum held in storage or away from the museum as part of a traveling show or on loan to another gallery. The location of art item at any given time is recorded as item status (D – display at museum, G-at Gallery, S-at show). Many of the art works may be part of a given show and loaned to gallery. Each gallery or show may have many items from the museum. CAN wants to retain a complete history of loaning a work of art to other galleries, and each time a work is loaned, the museum wants to know the date the art work was loaned and the date it was returned. CAN also wants to keep track of art work at show by recording date on which it was placed at show and returned from the show. As you develop the ERD for this problem, follow good data naming guidelines and database design principles. Draw ERD (Relational Model) using Oracle Data Modeler or any other Data Modeler. Define proper relationships among entities and resolve any composite or multivalued attributes. Within ERD, for each entity list all attributes and their datatypes and size, mandatory/optional, primary key and foreign key wherever applicable. Cleary state assumptions you have made (if any) for the ERD design.