Date Added: Jan 2013
When an attempt is made to modify tables that have not been sufficiently normalized undesirable side-effects may follow. This can be further specified as an update, insertion or deletion anomaly depending on whether the action that causes the error is a row update, insertion or deletion respectively. Most of the recent works on database normalization use a restricted definition of normal forms where only the primary key is taken into account and ignoring the rest of candidate keys. In this paper, the authors propose an algorithmic approach for database normalization up to third normal form by taking into account all candidate keys, including the primary key.