Scribd
Upload
1K views

Normalization Assignment

Normalization is the process of organizing data into tables to reduce duplication and dependency issues. A table should focus on one topic and include only related columns. A table is in first normal form (1NF) when all attributes depend on the primary key, in second normal form (2NF) when it is in 1NF and has no partial dependencies, and in third normal form (3NF) when it is in 2NF and has no transitive dependencies. Transitive dependencies occur when a non-key attribute depends on another non-key attribute.

Uploaded by

Naz
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
1K views

Normalization Assignment

Normalization is the process of organizing data into tables to reduce duplication and dependency issues. A table should focus on one topic and include only related columns. A table is in first normal form (1NF) when all attributes depend on the primary key, in second normal form (2NF) when it is in 1NF and has no partial dependencies, and in third normal form (3NF) when it is in 2NF and has no transitive dependencies. Transitive dependencies occur when a non-key attribute depends on another non-key attribute.

Uploaded by

Naz
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

What is normalization?

Normalization is the process used to organize a database into tables and columns. A table should
be about a specific topic and that only those columns, which support that topic, are included. By,
limiting a table to one purpose you reduce that number of duplicate data, which helps eliminate
some issues stemming from database modifications
When is a table in 1NF?
A table is in 1NF when all the key attributes are defined and when all remaining attributes are
dependent on the primary key.
When is a table in 2NF?
A table is in 2NF when it is in 1NF and it includes no partial dependencies.
When is a table in 3NF?
A table is in 3NF when it is in 2NF and it contains no transitive dependencies.
When is a table in BCNF?
A table is in BCNF when it is in 3NF and every determinant in the table is a candidate key.
Given the dependency diagram shown in Figure Q5.6, answer items 6a-6c:
a. Identify and discuss each of the indicated dependencies.
C1 C2 represents a partial dependency, because C2 depends only on C1, rather than on
the entire primary key composed of C1 and C3.
C4 C5 represents a transitive dependency, because C5 depends on an attribute (C4)
that is not part of a primary key.
C1, C3 C2, C4, C5 represents a set of proper functional dependencies, because C2,
C4, and C5 depend on the primary key composed of C1 and C3.

What is a partial dependency? With what normal form is it associated?


A partial dependency exists when an attribute is dependent on only a portion of the primary key.
This type of dependency is associated with 1NF.
What three data anomalies are likely to be the result of data redundancy? How can
such anomalies be eliminated?
The most common anomalies considered when data redundancy exists are: update anomalies,
addition anomalies, and deletion anomalies. All these can be eliminated through data
normalization. Data redundancy produces data integrity problems, caused by the fact that data
entry failed to conform to the rule that all copies of redundant data must be identical.
Define and discuss the concept of transitive dependency.
Transitive dependency is a condition in which an attribute is dependent on another attribute that
is not part of the primary key. This kind of dependency usually requires the decomposition of the
table containing the transitive dependency.
To remove a transitive dependency, the designer must perform the following actions:
Place the attributes that create the transitive dependency in a separate table.
Make sure that the new table's primary key attribute is the foreign key in the original
table.
What is a surrogate key, and when should you use one?
A surrogate key is an artificial PK introduced by the designer with the purpose of simplifying the
assignment of primary keys to tables. Surrogate keys are usually numeric and are often
automatically generated by the DBMS, they have no special meaning, and they are usually
hidden from the end users.
Why is a table whose primary key consists of a single attribute automatically in 2NF when
it is in 1NF?
A dependency based on only a part of a composite primary key is called a partial dependency.
So, if the PK is a single attribute, there can be no partial dependencies.
How would you describe a condition in which one attribute is dependent on another
attribute when neither attribute is part of the primary key?
A transitive dependency is a dependency of one nonprime attribute on another nonprime

attribute.
Suppose that someone tells you that an attribute that is part of a composite primary key is
also a candidate key. How would you respond to that statement?
This argument is incorrect if the composite PK contains no redundant attributes. If the composite
primary key is properly defined, all of the attributes that compose it are required to identify the
remaining attribute values. A candidate key is can be used to identify all of the remaining
attributes, but it was not chosen to be a PK for some reason.
A table is in ___ normal form when it is in ____ and there are no transitive dependencies.
3rd, 2nd normal form.

The relational schema may be written as follows:


ITEM (ITEM_ID, ITEM_DESCRIPTION, BLDG_ROOM, BLDG_CODE, BLDG_NAME,
BLDG_MANAGER)

b.
The relational schemas are written as follows:
EMPLOYEE( EMP_CODE, EMP_LNAME, EMP_FNAME, EMP_INITIAL)
BUILDING (BLDG_CODE, BLDG_NAME, EMP_CODE)
ITEM (ITEM_ID, ITEM_DESCRIPTION, ITEM_ROOM, BLDG_CODE)

c.

You might also like