Question 4. (20 points) Consider the table below where a certain firm is keeping

Question

Question 4. (20 points) Consider the table below where a certain firm is keeping track of temporary worker assignments. This is their only database, they store all relevant information in its single table. Each row corresponds to a single assignment, which is performed by a temporary worker who is identified by "Temp ID" and with name "Temp Name". Each assignment is done for a certain department identified by "Dept Code" and with name "Dept Name", and it consists on doing a certain job identified by "Job Code" and "Job Description". Each assignment also has a "Date", a certain number of hours ("Hours Spent"), and it is paid at a certain rate per hour ("Rate/Hour"). The rate per hour is negotiated separately for each assignment. Your goal is to redesign their single table database Below you have some rows of the table to help you understand the kind of data it stores, and how the data relates with itself. Assignment Temp Temp ID Job Job Dept Code Name Dept Hours Rate Spent /hour Code Description Date Consulting Consulting ID Name 1013 Bill WongENGEngineering TC Technica 2/27/2011 |3 $100 11765 1015 Melanie EMKTMarketing TC Technical 1/25/2011 |4 120 ast 11767 11768 11769 2051 Ed North ACT 2051 Ed North MKT 3356 John Accounting CLR Clerical Marketing CLR Clerical Sales 1/31/2011 |2 2/10/2011 4 SC Strategic 2/15/20115 $50 $55 $90 SLS Edokway Consulting $60 S65 $110 $70 3356 John MKT Marketing EDT Editing 3/20/2011|6 Edokway Estevez Goldberg Goldberg 4076Marissa ENG Engineering EDT Editing 2/26/2011 |7 11766 4079 HannahENGEngineering TC Technical 1/25/2011 |4 Consulting 4079 Hannah MKT MarketingEDT Editing 2/25/2011 5 a) What can go wrong with storing such information in a single table like the one above? Give one example of an insertion anomaly and of an update anomaly that can happen when using the table above

Explanation / Answer

This type of data storage causes inaccurate data and also there will be data redundency and also effects the performance when we want to access the data from this table. This will obviously leads to the inaccurate data in the database. When we want to store any information it doesn't store in a perticular way so that finally we get confused.
Also there will me all type of anomalies exists in this type of database. for example let us take the update anomaly. If we want to update the TempName of person ED North to North ED we will update the name. But there are other records existing in the table for that same person but the name wasnot updated . This results inconsistency in the database. This is called update anomaly.
If we consider insertion anomaly with this table we wanted to update some records related to job means new job code and description But the respective attributes doesn't have data in this case we can't update the table. This referes to the insert anomaly.

Related Questions

Navigate

• Browse (All)
• Browse Q
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.