KimTay Pet Supplies database design (see Figure 2-1) to support the following requirements. A customer is not necessarily represented by a single sales rep, but they can be represented by several sales reps. When a customer places an order, the sales rep who gets the commission on the invoice must be in the collection of sales reps who represent the customer. 2. Indicate the changes (using the shorthand representation) that you would need to make to the original KimTay Pet Supplies database design to support the following requiremen

Indicate the changes (using the shorthand representation) that you would need to make to the original KimTay Pet Supplies database design to support the following requirements. There is no relationship between customers and sales reps. When a customer places an order, any sales rep can process the order and create the invoice. On the invoice, you need to identify both the customer placing the order and the sales rep responsible for the invoice. Draw an E-R diagram for the new design.

You will need to create the database tables and choose sensible data types for each column.Make sure to maintain entity and referential integrity, and implement all the above constraints.Since other developers work in parallel on other parts of the system, you will need to strictly follow the above specification to correctly implemented in your database. Otherwise, the other software will not be able to use your database. This means, one needs to be able to rely on all constraints being correct, the spelling of table and column names being as given, and that the data types that you chose will allow for sensible data to be added to the database in the future.For testing purposes, you are asked to insert the data specified below into the tables, but no other data except this.In short:1. You will need to create the tables as specified2. You will need to add the data specified Please use the 3.sql and implement your tables using the sketched CREATE TABLE commands. Add the necessary queries…

Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram: The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names: All lower case Underscore separator between root and suffix Foreign keys have the same name as referenced primary key Write CREATE TABLE and ALTER TABLE statements that: Implement the entity as a new phone table. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables. Remove the existing phone column from the Sakila address table. Step 2 requires adding a foreign key constraint to an existing table. Ex: ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE; Specify data types as follows: phone_id, phone_number, and country_code have data type INT. phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'. Apply…