Use MS Visio to create relational data schemas and data dependency diagrams for all entities (tables). Start out with listing all data attributes in 1NF, then label partial dependencies and potential transitive dependencies. For this Data. A database for payment and bookings for a Virginia Beach hotel.  A guest can check into a hotel. A hotel can have many guests. A hotel can keep a record of a guest’s activities. A record can contain many notes. Possible tables might include: Guests, Notes, Room Type, Charges. Possible Primary keys might include: GuestID, NoteID, RoomID, ChargeCode. Possible attributes might include: CustName, Room#, ChargeType.

In this piece, you will get an understanding of the MongoDB data model and how it differs from the more common relational data model.

Produce a relational schema diagram that corresponds to the linked ER diagram for a database for the television show Saturday Night Live (SNL). Your relational schema diagram should include primary and foreign keys. Often-times in database system development, requirements will change after the conceptual data model has been drafted: in your rela- tional schema diagram, add the following three additional attributes: attribute “birth.date" for the relation schema Host; attribute “start.date" for the relation schema Writer; and attribute “salary" for relation schema Cast Member. Please refer back to the requirements in Question 6, for additional details that may constrain the design of the relational schema model. Use the tool linked to create an image. Hints: please carefully note that "rerun date", “address", and “phone" are multi-valued attributes; how would those be depicted in the relational schema diagram? Also, please carefully note the many-to-many relationships; how would those…

Give a justification for why a relational database cannot support many-to-many relationships, and support your position with an example?