- In your ERDs all many-to-many relationships must be resolved into two l:many relationships. - For each table you must clearly label the primary key attribute(s), the foreign key attribute(s) if any, and at least one non-key attribute. - For all ERDs, unless specified "Simplified ERD", you must provide as a minimum the PK, any FKs, one non-key attribute and any other attribute specifically required in each problem. 1. (20pts) Use the given DIRECTOR database for the following questions. a. Change a value in the PLAY table so that referential integrity is violated. Explain why your change leads to the violation. What is your change? Why will your change lead to a violation of referential integrity? b. Find the result of natural join of DIRECTOR and PLAY. Show ALL 3 intermediate results to get full credit. /2Nn+)T Tra halnirtahla th sprixar tran mustinne a. Give two examples (sources) of data redundancy in the given table. A source of redundancy is a subset of columns that tend to repeat within the table. Example1: Example2: b. Show why redundancy is undesirable by describing potential problems that may occur when one updates content of the table. To illustrate your case you must use an example/source from the ones you provided in answer to a. c. Show how you can remove the data redundancies by creating a new database where unnecessary redundancies are unlikely to occur. In your Crow's Foot ERD for the new database show all the tables and all the fields in each table. You should also show connectivity. Determine the optionality in each case by examining the actual data provided. Assume the given data fully represent all the requirements for the database. Your ERD must capture all the relationships you can detect in the given data. Must show all fields. Must label PK and FK