Preface to the Second Edition |
|
xiii | |
What You Need to Know |
|
xv | |
Acknowledgments |
|
xv | |
Part One: Theory |
|
|
|
3 | (8) |
|
Effects of Poor Database Design |
|
|
4 | (5) |
|
Unnecessary Duplicated Data and Data Consistency |
|
|
6 | (1) |
|
|
7 | (1) |
|
|
8 | (1) |
|
|
9 | (1) |
|
What You Will Find in This Book |
|
|
9 | (2) |
|
Entities and Data Relationships |
|
|
11 | (36) |
|
Entities and Their Attributes |
|
|
12 | (8) |
|
|
13 | (2) |
|
Single-Valued versus Multivalued Attributes |
|
|
15 | (2) |
|
Avoiding Collections of Entities |
|
|
17 | (1) |
|
Documenting Logical Data Relationships |
|
|
18 | (1) |
|
Entities and Attributes for Lasers Only |
|
|
19 | (1) |
|
|
20 | (3) |
|
|
21 | (1) |
|
|
21 | (2) |
|
|
23 | (10) |
|
|
24 | (2) |
|
One-to-Many Relationships |
|
|
26 | (1) |
|
Many-to-Many Relationships |
|
|
27 | (1) |
|
Weak Entities and Mandatory Relationships |
|
|
27 | (1) |
|
Documenting Relationships |
|
|
28 | (4) |
|
Basic Relationships for Lasers Only |
|
|
32 | (1) |
|
Dealing with Many-to-Many Relationships |
|
|
33 | (4) |
|
|
34 | (2) |
|
Documenting Composite Entities |
|
|
36 | (1) |
|
Resolving Lasers Only's Many-to-Many Relationships |
|
|
36 | (1) |
|
Relationships and Business Rules |
|
|
37 | (2) |
|
Data Modeling versus Data Flow |
|
|
39 | (4) |
|
|
43 | (1) |
|
|
44 | (3) |
|
|
47 | (26) |
|
|
48 | (6) |
|
|
48 | (2) |
|
|
50 | (2) |
|
Limitations of File Processing |
|
|
52 | (1) |
|
File Processing on the Desktop |
|
|
53 | (1) |
|
The Hierarchical Data Model |
|
|
54 | (5) |
|
Characteristics of the Hierarchical Data Model |
|
|
54 | (3) |
|
|
57 | (2) |
|
The Simple Network Data Model |
|
|
59 | (6) |
|
Characteristics of a Simple Network |
|
|
59 | (3) |
|
|
62 | (3) |
|
The Complex Network Data Model |
|
|
65 | (8) |
|
The Relational Data Model |
|
|
73 | (20) |
|
|
74 | (3) |
|
Columns and Column Characteristics |
|
|
75 | (1) |
|
Rows and Row Characteristics |
|
|
76 | (1) |
|
|
76 | (1) |
|
|
77 | (1) |
|
|
77 | (5) |
|
Primary Keys to Identify People |
|
|
78 | (2) |
|
Avoiding Meaningful Primary Keys |
|
|
80 | (1) |
|
Concatenated Primary Keys |
|
|
81 | (1) |
|
|
82 | (1) |
|
Representing Data Relationships |
|
|
82 | (4) |
|
|
85 | (1) |
|
Foreign Keys and Primary Keys in the Same Table |
|
|
86 | (1) |
|
|
86 | (2) |
|
|
86 | (1) |
|
|
87 | (1) |
|
|
88 | (2) |
|
Sample Data Dictionary Tables |
|
|
89 | (1) |
|
|
90 | (2) |
|
|
92 | (1) |
|
|
93 | (28) |
|
Translating an ER Diagram into Relations |
|
|
94 | (1) |
|
|
95 | (1) |
|
|
96 | (6) |
|
Understanding Repeating Groups |
|
|
97 | (1) |
|
Handling Repeating Groups |
|
|
98 | (2) |
|
Problems with First Normal Form |
|
|
100 | (2) |
|
|
102 | (4) |
|
Understanding Functional Dependencies |
|
|
103 | (1) |
|
Using Functional Dependencies to Reach 2NF |
|
|
104 | (1) |
|
Problems with 2NF Relations |
|
|
105 | (1) |
|
|
106 | (2) |
|
|
106 | (2) |
|
|
108 | (2) |
|
|
110 | (2) |
|
|
111 | (1) |
|
Normalized Relations and Database Performance |
|
|
112 | (7) |
|
|
113 | (3) |
|
What's Really Going On: PRODUCT and RESTRICT |
|
|
116 | (3) |
|
|
119 | (1) |
|
|
119 | (2) |
|
Database Structure and Performance Tuning |
|
|
121 | (8) |
|
|
122 | (2) |
|
Deciding Which Indexes to Create |
|
|
124 | (1) |
|
|
124 | (2) |
|
|
126 | (2) |
|
|
126 | (1) |
|
|
127 | (1) |
|
|
128 | (1) |
|
|
129 | (14) |
|
|
130 | (2) |
|
The Guaranteed Access Rule |
|
|
132 | (1) |
|
Systematic Treatment of Null Values |
|
|
133 | (1) |
|
Dynamic Online Catalog Based on the Relational Model |
|
|
134 | (1) |
|
The Comprehensive Data Sublanguage Rule |
|
|
135 | (1) |
|
|
136 | (1) |
|
High-Level Insert, Update, and Delete |
|
|
137 | (1) |
|
Physical Data Independence |
|
|
138 | (1) |
|
Logical Data Independence |
|
|
139 | (1) |
|
|
139 | (2) |
|
Distribution Independence |
|
|
141 | (1) |
|
|
142 | (1) |
|
|
143 | (34) |
|
An Introduction to Object-Oriented Concepts |
|
|
144 | (22) |
|
|
145 | (1) |
|
|
146 | (5) |
|
|
151 | (6) |
|
|
157 | (8) |
|
Benefits of Object Orientation |
|
|
165 | (1) |
|
Integrating Objects into a Relational Database |
|
|
166 | (1) |
|
ER Diagrams for Object-Relational Designs |
|
|
167 | (5) |
|
|
172 | (5) |
Part Two: Practice |
|
|
Using SQL to Implement a Relational Design |
|
|
177 | (38) |
|
Database Object Hierarchy |
|
|
178 | (3) |
|
Naming and Identifying Objects |
|
|
179 | (2) |
|
|
181 | (2) |
|
|
181 | (1) |
|
Identifying the Schema You Want to Use |
|
|
182 | (1) |
|
|
183 | (1) |
|
|
184 | (14) |
|
|
185 | (5) |
|
|
190 | (1) |
|
|
190 | (1) |
|
|
191 | (1) |
|
|
191 | (3) |
|
Additional Column Constraints |
|
|
194 | (4) |
|
|
198 | (3) |
|
Deciding Which Views to Create |
|
|
198 | (1) |
|
|
199 | (1) |
|
|
199 | (2) |
|
|
201 | (3) |
|
Creating Temporary Tables |
|
|
202 | (1) |
|
Loading Temporary Tables with Data |
|
|
203 | (1) |
|
Disposition of Temporary Table Rows |
|
|
203 | (1) |
|
|
204 | (1) |
|
Modifying Database Elements |
|
|
205 | (4) |
|
|
205 | (1) |
|
|
206 | (1) |
|
|
206 | (1) |
|
|
207 | (1) |
|
|
208 | (1) |
|
Deleting Database Elements |
|
|
209 | (1) |
|
Granting and Revoking Access Rights |
|
|
209 | (4) |
|
|
210 | (1) |
|
|
210 | (1) |
|
|
211 | (1) |
|
|
212 | (1) |
|
Object-Relational Extensions |
|
|
213 | (2) |
|
Using Case Tools for Database Design |
|
|
215 | (16) |
|
|
216 | (2) |
|
|
218 | (2) |
|
|
220 | (2) |
|
|
222 | (3) |
|
|
225 | (3) |
|
Sample Input and Output Designs |
|
|
228 | (1) |
|
|
229 | (1) |
|
|
230 | (1) |
|
Database Design Case Study #1: Mighty-Mite Motors |
|
|
231 | (50) |
|
|
232 | (19) |
|
Product Development Division |
|
|
232 | (6) |
|
|
238 | (1) |
|
Marketing & Sales Division |
|
|
239 | (1) |
|
Current Information Systems |
|
|
239 | (1) |
|
|
240 | (1) |
|
New Information Systems Division |
|
|
241 | (1) |
|
|
241 | (1) |
|
Current Business Processes |
|
|
242 | (9) |
|
|
251 | (17) |
|
|
253 | (3) |
|
|
256 | (5) |
|
|
261 | (1) |
|
|
262 | (6) |
|
The Object-Relational Design |
|
|
268 | (13) |
|
|
273 | (2) |
|
Using the Classes in the Schema |
|
|
275 | (6) |
|
Database Design Case Study #2: East Coast Aquarium |
|
|
281 | (40) |
|
|
282 | (8) |
|
|
284 | (4) |
|
The Volunteer Organization |
|
|
288 | (2) |
|
|
290 | (11) |
|
Creating the Application Prototype |
|
|
290 | (10) |
|
|
300 | (1) |
|
|
300 | (1) |
|
|
301 | (1) |
|
The Animal Tracking Database |
|
|
301 | (15) |
|
Highlights of the Application Prototype |
|
|
303 | (5) |
|
|
308 | (3) |
|
|
311 | (1) |
|
|
312 | (4) |
|
The Object-Relational Design |
|
|
316 | (5) |
|
|
316 | (1) |
|
The Animal Tracking Database |
|
|
317 | (4) |
|
Database Design Case Study #3: Independent Intelligence Agency |
|
|
321 | (54) |
|
|
322 | (11) |
|
Current Information Systems |
|
|
324 | (3) |
|
|
327 | (1) |
|
|
328 | (5) |
|
|
333 | (22) |
|
|
334 | (3) |
|
ER Diagram for Intelligence Gathering and Sales |
|
|
337 | (3) |
|
ER Diagram for System Security |
|
|
340 | (1) |
|
ER Diagram for Equipment Tracking |
|
|
341 | (2) |
|
|
343 | (1) |
|
|
344 | (11) |
|
The Object-Relational Design |
|
|
355 | (20) |
|
|
362 | (3) |
|
|
365 | (10) |
Glossary |
|
375 | (12) |
Index |
|
387 | |