Exam 6: Normalization of Database Tables

Dependencies based on only a part of a composite primary key are known as dependencies.

Explain normalization and its different forms.

Normalization should be part of the design process.

A table that displays data redundancies yields .

The provides the big picture, or macro view, of an organization's data requirements and operations.

From a structural point of view, 3NF is better than .

Dependencies that are based on only a part of a composite primary key are called transitive dependencies.

Data stored at their highest level of granularity are said to be atomic data.

Repeating groups must be eliminated by ensuring that each row defines a single entity.

Before converting a table into 3NF, it is imperative that the table already be in .

All relational tables satisfy the 1NF requirements.

For most business transactional databases, we should normalize relations into .

The combination of and ER modeling yields a useful ERD, whose entities may now be translated into appropriate table structures.

Because a partial dependency can exist only when a table's primary key is composed of several attributes, a table whose key consists of only a single attribute is automatically in 2NF once it is in 1NF.

A table that is in 1NF and includes no partial dependencies is said to be in .

In a real-world environment, changing granularity requirements might dictate changes in primary key selection, and those changes might ultimately require the use of keys.

What steps are involved in the conversion to third normal form?

An example of denormalization is using a denormalized table to hold report data. This is required when creating a tabular report in which the columns represent data that are stored in the table as rows.

Normalization represents a micro view of the within the ERD.

If you have three different transitive dependencies, different determinant(s) exist.