Scribd
Upload
11 views

IT476 - 1 Database Management System

gdfrt

Uploaded by

6Writers Experts
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views

IT476 - 1 Database Management System

gdfrt

Uploaded by

6Writers Experts
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

IT476-1 Database Management System

Discussion Questions

1. First normal form (1NF), second normal form (2NF) and third normal form (3NF) in

Database Normalization

First normal form (1NF) refers to a table that only contains indivisible values, with each cell

containing a single value, each column having a unique name and each row being unique

(Panwar, 2020). Relations in 1NF do not have multivalued attributes.

Second normal form (2NF) first requires a table to be in 1NF and should not have partial

dependency (Sudhindaran, 2017). This means that the subset of the candidate key is not

expected to result in a non-prime attribute.

A relation is considered to be in third normal form (3NF) when first it is in 2NF and the non-

prime attributes are non-transitively dependent on the candidate key (Panwar, 2020). In 2NF,

non-prime attributes are expected to be functionally dependent on the key but not dependent

on another non-prime attribute.

2. 3 Data Anomalies that are likely to be the result of data redundancy, and how they can

be eliminated

i) Update anomaly

This error occurs when some information is inconsistently added across different locations in

a database (Bailis et al., 2014). This results in inconsistent data appearing across a database.

This error can be eliminated by applying any change uniformly across a database.

ii) Insertion anomaly

This anomaly refers to when data cannot be expectedly inserted into a database when some

other related data is missing (Hussain et al., 2015). For example, a row cannot be
successfully created when some related information about its content is not present. This

anomaly can be eliminated by inserting complete sets of information across all rows and

columns of a database.

iii) Deletion anomaly

This error occurs when removing a particular record causes the unintentional removal of

other important data from the database (Hussain et al., 2015). An example is when removing

the details of a student results in removing the information of other students from the same

department. This anomaly can be eliminated by normalization, which is organizing data to

reduce dependency and redundancy. It can also be avoided by breaking down tables into

more manageable entities, and establishing relationships that ensure integrity.


References

Bailis, P., Fekete, A., Franklin, M. J., Ghodsi, A., Hellerstein, J. M., & Stoica, I. (2014).

Coordination avoidance in database systems (Extended version). arXiv preprint

arXiv:1402.2237.

Hussain, S. R., Sallam, A. M., & Bertino, E. (2015, March). Detanom: Detecting anomalous

database transactions by insiders. In Proceedings of the 5th ACM Conference on Data

and Application Security and Privacy (pp. 25-35).

Panwar, V. (2020, June). Database Normalization: A Review. In International Journal for

Research Publication and Seminar (Vol. 11, No. 2, pp. 4-16).

Sudhindaran, D. S. (2017). Generating a Normalized Database Using Class Normalization.

You might also like