Examples of Anomalies
(Updated Oct 2004)
Emp_ID |
L_Name |
F_Name |
Dept_Name |
Salary |
Course_Title |
Date_Completed |
100 |
Simpson |
Margaret |
Marketing |
48000 |
SPSS |
|
100 |
Simpson |
Margaret |
Marketing |
48000 |
Surveys |
|
140 |
Morton |
Alan |
Accounting |
52000 |
Tax Acct |
|
150 |
Martin |
Susan |
Marketing |
42000 |
SPSS |
|
150 |
Martin |
Susan |
Marketing |
42000 |
Java |
|
190 |
Davis |
Larry |
Finance |
55000 |
|
|
1. Insertion anomaly: to insert a new employee, the user must supply the values for both of the key fields Emp_ID and Course_Title – however, in a normal business situation, a new employee (such as #190 above) should be allowed to be added w/o the need of a course.
2. Deletion anomaly: what would happen to the course "Tax Acct" if Emp # 140 is to be deleted?
3. Modification anomaly: suppose Emp # 150 receives a
salary raise, then how many rows need to be updated – and
what if one of them
is missed?
à
à
à
à à à
To solve the above problems, normalization is
employed.