FiltersDone

Question type

Essay

Multiple Choice

Short Answer

True False

Matching

Exam 6: Normalization of Database Tables

Show Answer

Share

---

All types

Filters

Study FlashcardsPractice ExamLearn

Question 21

Essay

Review LaterAdd Note

Review Later

Explain normalization and its different forms.

Correct Answer

verified

Normalization is a process for evaluatin...

View Answer

Show Answer

Question 22

Multiple Choice

Review LaterAdd Note

Review Later

Normalization represents a micro view of the within the ERD.

A) entities
B) attributes
C) relationships
D) forms

E) B) and D)
F) C) and D)

Correct Answer

verified

Show Answer

Question 23

True/False

Review LaterAdd Note

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

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

Normalization should be part of the design process.

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

All relational tables satisfy the 1NF requirements.

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

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 .

A table that displays data redundancies yields .

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

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

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

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.

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

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.

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

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.

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