Exam 6: Normalization of Database Tables

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

The advantage of higher processing speed must be carefully weighed against the disadvantage of data anomalies.

Normalization represents a micro view of the entities within the ERD.

In order to meet performance requirements,portions of the database design may need to be occasionally denormalized.

Data warehouse routinely uses structures in its complex,multilevel,multisource data environment.

If database tables are treated as though they were files in a file system,the never has a chance to demonstrate its superior data-handling capabilities.

A table where every determinant is a candidate key is said to be in .

Relational models view data as part of a table or collection of tables in which all key values must be identified.

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

The is central to a discussion of normalization.

Unnormalized tables yield no simple strategies for creating virtual tables known as .

A table is in BCNF if every determinant in the table is a foreign key.

Of the following normal forms,is mostly of theoretical interest.

The most likely data type for a surrogate key is .

In the context of partial dependencies,data redundancies occur because every row entry requires duplication of data.

Unnormalized database tables often lead to various data redundancy disasters in production databases.

Improving leads to more flexible queries.

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

To generate a surrogate key,Microsoft Access uses a(n)data type.

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