Database Redesign - Database Processing: Fundamentals, Design, and Implementation - page 387

8.13 Explain how the words any and all pertain to the SQL keywords EXISTS and NOT
EXISTS.
8.14 Explain the processing of the query on page 372.
8.15 Using the View Ridge Gallery database, write a query that will display the names of any
customers who are interested in all artists.
8.16 Explain how the query in your answer to Review Question 8.15 works.
8.17 Why is it important to analyze the database before implementing database redesign
tasks? What can happen if this is not done?
8.18 Explain the process of reverse engineering.
8.19 Why is it important to carefully evaluate the results of reverse engineering?
8.20 What is a dependency graph? What purpose does it serve?
8.21 Explain the dependencies for WORK in the graph in Figure 8-3.
8.22 What sources are used when creating a dependency graph?
8.23 Explain two different types of test databases that should be used when testing data-
base redesign changes.
8.24 Explain the problems that can occur when changing the name of a table.
8.25 Describe the process of changing a table name.
8.26 Considering Figure 8-3, describe the tasks that need to be accomplished to change the
name of the table WORK to WORK_VERSION2.
8.27 Explain how views can simplify the process of changing a table name.
8.28 Under what conditions is the following SQL statement valid?
INSERT INTO T1 (A, B)
SELECT (C, D) FROM T2;
8.29 Show an SQL statement to add an integer column C1 to the table T2. Assume that C1
is NULL.
8.30 Extend your answer to Review Question 8.29 to add C1 when C1 is to be NOT NULL.
8.31 Show an SQL statement to drop the column C1 from table T2.
8.32 Describe the process for dropping primary key C1 and making the new primary key C2.
8.33 Which data type changes are the least risky?
8.34 Which data type changes are the most risky?
8.35 Write an SQL statement to change a column C1 to Char(10) NOT NULL. What condi-
tions must exist in the data for this change to be successful?
8.36 Explain how to change the minimum cardinality when a child that was required to
have a parent is no longer required to have one.
8.37 Explain how to change the minimum cardinality when a child that was not required to
have a parent is now required to have one. What condition must exist in the data for
this change to work?
8.38 Explain how to change the minimum cardinality when a parent that was required to
have a child is no longer required to have one.
8.39 Explain how to change the minimum cardinality when a parent that was not required
to have a child is now required to have one.
8.40 Describe how to change the maximum cardinality from 1:1 to 1:N. Assume that the
foreign key is on the side of the new child in the 1:N relationship.