Exam 6: Normalization of Database Tables

The objective of normalization is to ensure that each table conforms to the concept of well-formed relations.

yields better performance.

In the , no row may contain two or more multivalued facts about an entity.

Normalization is a very important database design ingredient, and the highest level is always the most desirable.

A dependency based on only a part of a composite primary key is called a .

Data redundancy produces data anomalies.

Dependencies can be identified with the help of a dependency .

is a process to help reduce the likelihood of data anomalies.

databases reflect the ever-growing demand for greater scope and depth in the data on which decision support systems increasingly rely.

Dependency diagrams are very helpful in getting a bird's-eye view of all the relationships among a table's attributes.

A table is in fourth normal form if it is in third normal form and has no independent multivalued dependencies.

A relational table must not contain a(n) .

Normalization purity is often easy to sustain in the modern database environment.

A(n) exists when there are functional dependencies such that XY is functionally dependent on WZ, X is functionally dependent on W, and XY is the primary key.

Attribute A attribute B if all of the rows in the table that agree in value for attribute A also agree in value for attribute B.

The price paid for increased performance through denormalization is a larger amount of .

The problem with transitive dependencies is that they still yield data .

Atomic attributes are attributes that can be further subdivided.

Most designers consider the BCNF as a special case of the .

In order to meet requirements, you may have to denormalize some portions of a database design.