CHAPTER FOUR
DATABASE DESIGN USING NORMALIZATION
True-False Questions
1.
When you are given a set of tables and asked to create a database to store their data, the first step
is to assess the tables' structure and content.
Answer:
True
Page:
102
2.
The first step in assessing table structure is to count rows and examine columns.
Answer:
True
Page:
102-103 [And see Figure 4-1]
3.
To count the number of rows in a table, use the SQL construct COUNT(ROWS).
Answer:
False
Page:
102
4.
To determine the number and type of columns in a table, use the SQL construct COUNT(*).
Answer:
False
Page:
102
5.
To limit the number of rows retrieved from a table, use the SQL keyword TOP.
Answer:
True
Page:
102
6.
The second step in assessing table structure is to examine data values and determine
dependencies and keys.
Answer:
True
Page:
102-103 [And see Figure 4-1]
7.
When examining data values as a part of assessing table structure, you should try to determine
functional dependencies.
Answer:
True
Page:
102 [And see Figure 4-1]
8.
When examining data values as a part of assessing table structure, you should try to determine
multivalued dependencies.
Answer:
True
Page:
102 [And see Figure 4-1]
9.
When examining data values as a part of assessing table structure, you should try to determine the
table's primary key.
Answer:
True
Page:
102 [And see Figure 4-1]
¶10.
When examining data values as a part of assessing table structure, there is no need to try to
determine candidate keys other than the table's primary key.
Answer:
False
Page:
102 [And see Figure 4-1]
11.
When examining data values as a part of assessing table structure, there is no need to try to
determine foreign keys.
Answer:
False
Page:
102 [And see Figure 4-1]
Page 4-1
This
preview
has intentionally blurred sections.
Sign up to view the full version.
Chapter Four
–
Database Design Using Normalization
12.
The third step in assessing table structure is to check the validity of presumed referential integrity
constraints.
Answer:
True
Page:
102-103 [And see Figure 4-1]
13.
Database design varies depending on whether you're building an updateable database or a read-
only database.
Answer:
True
Page:
102
14.
Normalization eliminates modification anomalies and data duplication.
Answer:
False
Page:
103 [And see Figure 4-2]
15.
The presence of one or more foreign keys in a relation means that we cannot eliminate duplicated
data in that table.
Answer:
True
Page:
103
16.
Normalization requires applications to use more complex SQL since they will need to write
subqueries and joins to recombine data stored in separate relations.
Answer:
True
Page:
104 [And see Figure 4-2]
17.
The standard sales order/line item pattern is a classic example of unneeded normalization.
Answer:
False
Page:
105
18.
Multivalued dependencies create anomalies so serious that multivlaued dependencies must
always be eliminated.
Answer:
True
Page:
106
19.
To eliminate multivalued dependencies, normalize your tables so that they are all in BCNF.
This is the end of the preview.
Sign up
to
access the rest of the document.
- Spring '08
- Plebani
- Relational model, Database normalization, BCNF, Denormalization d.
-
Click to edit the document details
