Thank you!!!

GBP now has offices in four international locations: Boston (is also the headquarters), Shanghai, Paris, and Vancouver are three international offices. The database structure remains the same except that the Publishing City attribute of the BOOK relation now indicates in which of the four offices the book record is located.

GBP has decided to reconfigure its database as a distributed database among its four offices for their books. Distributed and replicated among these four offices, the tables have the following characteristics:

The AUTHOR table consists of 6,000 records. The entire table is heavily used in the Boston headquarters for centralize the review process as well as advertising. However the records of individual authors are also used frequently in the international offices where their authored books are published.

The BOOK table consists of 80,000 records and is used most heavily in the international offices where the books are published. The headquarters also uses the BOOK table, but do not take the responsibility of maintenance. EDITSTAFF table consists of 60,000 records with a situation similar to the BOOK table. The EDITINGJOB data have a huge volume, and are used and updated with the data of BOOK and EDITSTAFF. In other words, the three tables are treated in the similar way.

Design a distributed relational database for GBP. Specify (using a data deployment matrix or a data deployment graph) your design of data deployment placement, partitioning (H. P. or V.P.), and replication for AUTHOR, BOOK, EDITSTAFF, and EDITINGJOB. (3.5 point)

Q5. Follow the GBP database case in Q3. BOOK Book Year BookCity SBN BookTitle Book Category AUTHOR "AuthorID AuthorName AuthorAdd Author Phone AuthorEmail AUTHORSHIP *ISBN Authororder "AuthortD EDITSTAFF EmployeeTitle "EmployeeID EmployeeName SupervisorlD EmployeeYear EDITING JOB "EmployeeID *ISBN Start Date EndDate Job Type