Then,

Use ERDPlus again to map the ER diagram you just created (ER diagram for Tbay Motors) into its corresponding relational schema. Make sure to clearly show all resulting relations and columns. Clearly indicate all primary keys (underline them) and all referential integrity constraints (i.e., foreign keys) using a line pointing from a foreign key to its source.

Question: How many entities are in the ER diagram, and how many relations are in the relational schema? Tell the reason why the two numbers are the same or different?

Create an ER diagram based on the following requirements. Make sure to clearly show entities, relationships, and attributes: Tbay Motors is a car dealership that will use a database to keep track of: - For each sales employee: salesname, startdate, number of years with dealership (yearswith), unique salessin, unique salesid. - For each service employee: servicename, unique servicesin, unique serviceid. - For each customer: unique cid, cname (composed of first name cfname and last name clname), one or more phonenumbers, and email (optional). For each vehicle: year, make, model, mileage, unique vin. For each repair appointment: radate, unique raid. Additional requirements: A sales employee must have at least one assigned customer but can have many assigned customers. Each customer is assigned to one sales employee. A vehicle is owned by exactly one customer. Each customer owns at least one vehicle but may own many. A vehicle may have many repair appointments but does not have to have any. Each repair appointment is associated with one vehicle. Each service employee participates in between zero and many repair appointments. Each repair appointment has at least one service employee participating in it but can have up to three service employees participating in it. Each sales employee selects one service employee as their tech expert. A service employee can be assigned to up to two sales employees as a tech expert, but does not have to be assigned to any