The database with five tables is described as follows.

CLIENT

*ClientID

ClientName

ClientAddress

ClientPhone

ClientEmail

RESERVATION

*ClientID

*RoomID

*ReservationDate

Check-inDate

Check-outDate

ROOM

*RoomID

RoomType

RoomLocation

RoomPrice

JANITOR

*EmployeeID

EmployeeName

EmployeeTitle

EmployeeYear

SupervisorID

CLEANING

*EmployeeID

*RoomID

*CleanDate

*CleanTime

JobType

GHC now has branches in four local regions: Boston (also the GHC headquarters), New York, Toronto, and Vancouver. The database structure remains the same except that the Location attribute of the ROOM relation now indicates in which of the four regions the room is located.

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

The CLIENT table consists of 600,000 records. The entire table is heavily used and maintained in the Boston headquarters for centralize the reservation process as well as customer surveys and advertising. However the records of individual clients are used frequently in the branches at which the hotel rooms are reserved.

The ROOM table consists of 6,000 records and is used most heavily in the branches for their regions in which the individual hotels are located. The headquarters also uses the ROOM table occasionally, but does not maintain it. The JANITOR table consists of 60,000 records with a situation similar to the ROOM table. The CLEANING data have a huge volume, and are used and updated with the data of ROOM and JANIOR. In other words, the three tables are treated in the similar way

Design a distributed relational database for GHC. Specify your design of data deployment placement, partitioning (H. P. or V.P.), and replication for CLIENT, ROOM, CLEANING, and JANITOR (using a data deployment matrix). (3.5 point)