Exam 6: Normalization of Database Tables

Any attribute whose value determines other values within a row is known as a .

refers to the level of detail represented by the values stored in a table's row.

When a table contains only one candidate key, are considered to be equivalent.

All relational tables satisfy the requirements.

When a nonkey attribute is the determinant of a key attribute, the table is in 3NF but not in .

The combination of normalization and ER modeling yields a useful ERD, whose entities can be translated into appropriate relationship structures.

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

Normalization works through a series of stages called normal forms.

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

BCNF can be violated only if the table contains more than one key.

The most likely data type for a surrogate key is .

Improving leads to more flexible queries.

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

When designing a new database structure based on the business requirements of the end users, the database designer will construct a data model using a technique such as .

A table is in 2NF if it is in 1NF, and it includes no partial dependencies.

According to the data-modeling checklist, should be nouns that are familiar to business, should be short and meaningful, and should document abbreviations, synonyms, and aliases for each entity.

When designing a database, you should .

Data redundancy produces .

A table is in 4NF if it is in 3NF, and .

1NF, 2NF, and 3NF are .