Chapter 4 Flashcards
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.
True
The first step in assessing table structure is to count rows and examine columns.
True
To count the number of rows in a table, use the SQL construct COUNT(ROWS).
False
To determine the number and type of columns in a table, use the SQL construct COUNT(*).
False
To limit the number of rows retrieved from a table, use the SQL TOP keyword.
True
When examining data values as a part of assessing table structure, you should try to determine two types of dependencies: functional dependencies and functional dependencies.
True
When examining data values as a part of assessing table structure, you should try to determine three types of keys: the primary key, any candidate keys and any foreign keys.
True
The second step in assessing table structure is to examine data values and determine dependencies and keys.
True
When examining data values as a part of assessing table structure, you should try to determine functional dependencies.
True
When examining data values as a part of assessing table structure, you should try to determine multivalued dependencies.
True
When examining data values as a part of assessing table structure, you should try to determine the table’s primary key.
True
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.
False
When examining data values as a part of assessing table structure, there is no need to try to determine foreign keys.
False
The third step in assessing table structure is to check the validity of presumed referential integrity constraints.
True
The elimination of modification anomalies and the reduction of duplicated data are advantages of normalization.
True
Database design varies depending on whether you’re building an updatable database or a read-only database.
True
Normalization eliminates modification anomalies and data duplication.
False
The presence of one or more foreign keys in a relation means that we cannot eliminate duplicated data in that table.
True
Normalization requires applications to use more complex SQL since they will need to write subqueries and joins to recombine data stored in separate relations.
True
Relations are sometimes left unnormalized to improve performance.
True
Relations in BCNF have no modification anomalies in regard to functional dependencies.
True
A defining requirement for BCNF is that every determinant must be a candidate key.
True
The SQL INSERT statement can be used to populate normalized tables.
True
The SQL DELETE TABLE statement can be used to remove unneeded tables after the normalized tables are created and populated.
False
SQL statements that can be used to create referential integrity statements for normalized tables are created during the normalization process.
True
The standard sales order/line item pattern is a classic example of unneeded normalization.
False
Multivalued dependencies create anomalies so serious that multivalued dependencies must always be eliminated.
True
Writing SQL subqueries and joins against normalized tables is simple compared to the code that must be written to handle anomalies from multivalued dependencies.
True
To eliminate multivalued dependencies, normalize your tables so that they are all in BCNF.
False
Creating a read-only database is a job often given to beginning database professionals.
True
Read-only databases are often updated.
False
Design guidelines and priorities are the same whether you’re working with an updatable database or a read-only database.
False
Normalization is an advantage for a read-only database.
False
Denormalization is the process of joining previously normalized tables back together.
True
Denormalization reduces the complexity of the SQL statements needed in an application to read required data.
True
Denormalization is simple—join the data together and store it in a table.
True