Overview Because information changes rapidly, monitoring and reviewing it is critical. It’s important for data analysts and scientists to be able to add or delete records due to the changing nature of information. Another benefit to working with data is identifying relationships that exist between different entities. For example, manufacturers might want to identify why their equipment came back, where it came from, or how long customers took to return it, along with a host of other reasons. Prompt In this lab, you will be using an existing database that is preloaded into Codio from MYSQLTutorial.org. You will need to compare records from different locations, identify cardinality, delete records, and reflect on the value of these skills. You will also need to articulate how cardinality can be applied and what its benefits are. All your screenshots and written responses need to be placed in the Cardinality and Targeted Data Template Word Document that goes with this assignment. Reference MySQLTutorial. (n.d.). MySQL sample database classicmodels [Data file]. Available from https://www.mysqltutorial.org/mysql-sample-databas...  Before you begin, load the “classicmodels” data set: Start a terminal session and run this command: mysql < mysqlsampledatabase.sql Type mysql in the command line and begin working with SQL the way you have been in previous labs. Write commands to use the classicmodels database and show its tables to verify that you’re in the right place. Retrieve employee tuples and identify the number of employees in San Francisco and New York. Command for San Francisco: select firstName, lastName, jobTitle, offices.city from employees inner join offices on employees.officeCode = offices.officeCode where state = 'CA'; Write and run a command to return records from New York on your own. Validate the completion of this step with a screenshot of these two tables. Retrieve order details for order Number 10330, 10338, and 10194 by running SELECT queries with WHERE clauses against the orders table. Validate the completion of this step with a screenshot. Then, reference the Module Four Lab ERD to assist in identifying relationships. A version with alternative text is available: Module Four Lab ERD With Alternative Text. Now, identify what type of cardinality this represents in the entity relationship model. Delete records from the payments table where the customer number equals 103. Run a describe statement to identify fields in the payments table first. Select the records from the payments table for customer number 103 before deleting them. Validate that the above instructions have worked with a screenshot. Delete the records from the payments table for customer number 103. Run a SELECT statement against the table to show that customer number 103 is no longer there. Validate the completion of this step with a screenshot. Retrieve customer records for employee Rep Barry Jones and identify relationships. Remember: SELECT, FROM, Inner Join, and WHERE. Use Barry’s employeeNumber, 1504, and perform a join between the customer salesRepEmployeeNumber to retrieve these records. Identify if these entities demonstrate one-to-one or one-to-many relationships. Retrieve records for customers who reside in Massachusetts, then identify their sales rep and the relationship of entities. Remember: SELECT, FROM, Inner Join, and WHERE. Use employee.firstName and employee.lastName in your command. Identify if these entities demonstrate one-to-one or many-to-many relationships. Add one customer record with your last name using an INSERT statement. You may use the name of a celebrity or fictional character if you don’t use your own name. Think of this as your signature. Complete these actions to get to the right place to enter this information: (1)Show databases, (2)use classicmodels, (3)show tables, (4)describe customers; You should now be seeing all of the fields that you’ll need to fill in to complete this step. Reference your Module Two lab or resources on how to populate these fields if you need to. Fields you’ll need to populate: customerNumber, customerName, contactLastName, contactFirstName, phone, addressLine1, addressLine2, city, state, postalCode, country, salesRepEmployeeNumber, creditLimit You will need to look up a valid salesRepEmployeeNumber in the employee table to populate salesRepEmployeeNumber. Run a select statement on the customers table, capture it in a screenshot, and put it in your template. Reflection: Use the lab environment or the screenshots you’ve worked with for this step. To retrieve information you were previously working with, run the mysql < mysqlsampledatabase.sql script. Define how cardinality is applied to the databases you’ve been working with and why different numbers of records returned from the different offices. Compare and contrast the different queries you ran and how cardinality applies to them. Describe two of the crucial benefits of cardinality in this type of database.