Preface |
|
xxiii | |
|
Part I The Context of Database Management |
|
|
|
|
2 | (1) |
|
|
3 | (82) |
|
|
3 | (1) |
|
|
3 | (1) |
|
|
4 | (2) |
|
Basic Concepts and Definitions |
|
|
6 | (4) |
|
|
6 | (1) |
|
|
6 | (1) |
|
|
7 | (1) |
|
Database Management Systems |
|
|
8 | (1) |
|
|
8 | (1) |
|
|
9 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
Traditional File Processing Systems |
|
|
10 | (1) |
|
File Processing Systems At Pine Valley Furniture Company |
|
|
11 | (2) |
|
Disadvantages of File Processing Systems |
|
|
11 | (1) |
|
|
12 | (1) |
|
|
12 | (1) |
|
|
12 | (1) |
|
Lengthy Development Times |
|
|
12 | (1) |
|
Excessive Program Maintenance |
|
|
12 | (1) |
|
|
13 | (1) |
|
Advantages of The Database Approach |
|
|
14 | (2) |
|
Program-Data Independence |
|
|
14 | (1) |
|
|
14 | (1) |
|
Improved Data Consistency |
|
|
14 | (1) |
|
|
14 | (1) |
|
Increased Productivity of Application Development |
|
|
14 | (1) |
|
|
15 | (1) |
|
|
15 | (1) |
|
Improved Data Accessibility and Responsiveness |
|
|
15 | (1) |
|
Reduced Program Maintenance |
|
|
15 | (1) |
|
Improved Decision Support |
|
|
16 | (1) |
|
Cautions About Database Benefits |
|
|
16 | (34) |
|
Managing the People Involved in Database Development |
|
|
50 | (2) |
|
Three-Schema Architecture for Database Development |
|
|
52 | (4) |
|
|
52 | (1) |
|
|
52 | (1) |
|
|
52 | (2) |
|
|
54 | (1) |
|
|
54 | (1) |
|
|
54 | (1) |
|
|
54 | (1) |
|
Strategies for Development |
|
|
54 | (2) |
|
Three-Tiered Database Location Architecture |
|
|
56 | (1) |
|
Developing A Database Application For Pine Valley Furnitury Company |
|
|
57 | (13) |
|
Simplified Project Data Model Example |
|
|
59 | (3) |
|
A Current Pine Valley Furniture Company Project Request |
|
|
62 | (1) |
|
Matching User Needs to the Information Systems Architecture |
|
|
62 | (3) |
|
Analyzing Database Requirements |
|
|
65 | (1) |
|
|
66 | (2) |
|
|
68 | (2) |
|
Administering the Database |
|
|
70 | (1) |
|
|
70 | (1) |
|
|
71 | (5) |
|
|
71 | (1) |
|
|
71 | (1) |
|
|
72 | (2) |
|
|
74 | (1) |
|
|
74 | (1) |
|
|
75 | (1) |
|
|
75 | (1) |
|
Case: Mountain View Community Hospital |
|
|
76 | (8) |
|
|
|
|
84 | (1) |
|
Modeling Data in the Organization |
|
|
85 | (54) |
|
|
85 | (1) |
|
|
85 | (2) |
|
Modeling the Rules of the Organization |
|
|
87 | (6) |
|
Overview of Business Rules |
|
|
87 | (1) |
|
The Business Rules Paradigm |
|
|
88 | (1) |
|
|
88 | (1) |
|
|
89 | (1) |
|
|
89 | (1) |
|
Data Names and Definitions |
|
|
90 | (1) |
|
|
90 | (1) |
|
|
91 | (1) |
|
|
91 | (2) |
|
The E-R Model: An Overview |
|
|
93 | (3) |
|
|
93 | (2) |
|
|
95 | (1) |
|
Modeling Entities and Attributes |
|
|
96 | (10) |
|
|
96 | (1) |
|
Entity Type Versus Entity Instance |
|
|
96 | (1) |
|
Entily Type Versus System Input, Output, or User |
|
|
96 | (1) |
|
Strong Versus Weak Entity Types |
|
|
97 | (1) |
|
Naming and Defining Entity Types |
|
|
98 | (2) |
|
|
100 | (1) |
|
Required Versus Optional Attributes |
|
|
100 | (1) |
|
Simple Versus Composite Attributes |
|
|
101 | (1) |
|
Single-Valued Versus Multivalued Attributes |
|
|
102 | (1) |
|
Stored Versus Derived Attributes |
|
|
102 | (1) |
|
|
103 | (1) |
|
Naming and Defining Attributes |
|
|
104 | (2) |
|
|
106 | (17) |
|
Basic Concepts and Definitions in Relationships |
|
|
107 | (1) |
|
Attributes on Relationships |
|
|
107 | (1) |
|
|
107 | (2) |
|
|
109 | (1) |
|
|
109 | (3) |
|
|
112 | (1) |
|
|
112 | (1) |
|
|
113 | (2) |
|
|
115 | (1) |
|
|
115 | (1) |
|
|
115 | (1) |
|
|
116 | (1) |
|
|
117 | (1) |
|
Modeling Time-Dependent Data |
|
|
117 | (3) |
|
|
120 | (1) |
|
Naming and Defining Relationships |
|
|
121 | (2) |
|
E-R Modeling Example: Pine Valley Furniture Company |
|
|
123 | (2) |
|
Database Processing At Pink Valley Furniture |
|
|
125 | (3) |
|
Showing Product Information |
|
|
125 | (1) |
|
Showing Customer Information |
|
|
126 | (1) |
|
Showing Customer Order Status |
|
|
126 | (1) |
|
|
127 | (1) |
|
|
128 | (1) |
|
|
129 | (8) |
|
|
129 | (1) |
|
|
129 | (2) |
|
|
131 | (4) |
|
|
135 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
|
136 | (1) |
|
Case: Mountain View Community Hospital |
|
|
137 | (2) |
|
The Enhanced E-R Model and Business Rules |
|
|
139 | (48) |
|
|
139 | (1) |
|
|
139 | (1) |
|
Representing Supertypes and Subtypes |
|
|
140 | (7) |
|
Basic Concepts and Notation |
|
|
141 | (2) |
|
|
143 | (1) |
|
|
144 | (1) |
|
When to Use Supcrtype/Subtype Relationships |
|
|
144 | (1) |
|
Representing Specialization and Generalization |
|
|
145 | (1) |
|
|
145 | (1) |
|
|
146 | (1) |
|
Combining Specialization and Generalization |
|
|
146 | (1) |
|
Specifying Constraints in Supertype/Subtype Relationships |
|
|
147 | (6) |
|
Specifying Completeness Constraints |
|
|
147 | (1) |
|
Total Specialization Rule |
|
|
148 | (1) |
|
Partial Specialization Rule |
|
|
149 | (1) |
|
Specifying Disjointness Constraints |
|
|
149 | (1) |
|
|
150 | (1) |
|
|
150 | (1) |
|
Defining Subtype Discriminators |
|
|
150 | (1) |
|
|
150 | (1) |
|
|
151 | (1) |
|
Defining Supertype/Subtype Hierarchies |
|
|
152 | (1) |
|
|
152 | (1) |
|
Summary of Supertype/Subtype Hierarchies |
|
|
153 | (1) |
|
EER Modling Example: Pine Valley Furniture |
|
|
153 | (4) |
|
|
157 | (3) |
|
|
160 | (6) |
|
|
166 | (8) |
|
Classification of Business Rules |
|
|
166 | (2) |
|
Stating a Structural Assertion |
|
|
168 | (1) |
|
|
169 | (1) |
|
Stating an Action Assertion |
|
|
169 | (1) |
|
Types of Action Assertions |
|
|
170 | (1) |
|
Representing and Enforcing Business Rules |
|
|
170 | (1) |
|
|
171 | (1) |
|
Identifying and Testing Business Rules |
|
|
172 | (2) |
|
|
174 | (1) |
|
|
175 | (6) |
|
|
175 | (1) |
|
|
175 | (1) |
|
|
176 | (3) |
|
|
179 | (1) |
|
|
179 | (1) |
|
|
180 | (1) |
|
|
180 | (1) |
|
Case: Mountain View Community Hospital |
|
|
181 | (5) |
|
|
|
|
186 | (1) |
|
Logical Database Design and the Relational Model |
|
|
187 | (53) |
|
|
187 | (1) |
|
|
187 | (1) |
|
The Relational Data Model |
|
|
188 | (5) |
|
|
188 | (1) |
|
Relational Data Structure |
|
|
189 | (1) |
|
|
189 | (1) |
|
|
190 | (1) |
|
Removing Multivalued Attributes from Tables |
|
|
190 | (1) |
|
|
191 | (2) |
|
|
193 | (4) |
|
|
193 | (1) |
|
|
193 | (1) |
|
|
194 | (1) |
|
|
195 | (1) |
|
Creating Relational Tables |
|
|
195 | (1) |
|
Well-Structured Relations |
|
|
196 | (1) |
|
Transforming EER Diagrams into Relations |
|
|
197 | (14) |
|
Step 1: Map Regular Entities |
|
|
198 | (1) |
|
|
198 | (1) |
|
|
199 | (1) |
|
Step 2: Map Weak Entities |
|
|
200 | (1) |
|
Step 3: Map Binary Relationships |
|
|
201 | (1) |
|
Map Binary One-to-Many Relationships |
|
|
201 | (1) |
|
Map Binary Many-to-Many Relationships |
|
|
202 | (1) |
|
Map Binary One-to-One Relationships |
|
|
202 | (1) |
|
Step 4: Map Associative Entities |
|
|
203 | (1) |
|
|
204 | (1) |
|
|
204 | (1) |
|
Step 5: Map Unary Relationships |
|
|
205 | (1) |
|
Unary One-to-Many Relationships |
|
|
205 | (1) |
|
Unary Many-to-Many Relationships |
|
|
206 | (1) |
|
Step 6: Map Ternary (and n-ary) Relationships |
|
|
207 | (1) |
|
Step 7: Map Supertype/Subtype Relationships |
|
|
208 | (2) |
|
Summary of EER to Relational Transformations |
|
|
210 | (1) |
|
Introduction to Normalization |
|
|
211 | (3) |
|
|
211 | (1) |
|
Functional Dependencies and Keys |
|
|
212 | (1) |
|
|
213 | (1) |
|
|
213 | (1) |
|
Normalization Example: Pine Valley Furniture Company |
|
|
214 | (6) |
|
Step 0: Represent the View in Tabular Form |
|
|
214 | (1) |
|
Step 1: Convert to First Normal Form |
|
|
214 | (1) |
|
|
215 | (1) |
|
|
215 | (2) |
|
|
217 | (1) |
|
Step 2: Convert to Second Normal Form |
|
|
217 | (1) |
|
Step 3: Convert to Third Normal Form |
|
|
218 | (1) |
|
Removing Transitive Dependencies |
|
|
218 | (2) |
|
Determinants and Normalization |
|
|
220 | (1) |
|
Step 4: Further Normalization |
|
|
220 | (1) |
|
|
220 | (3) |
|
|
221 | (1) |
|
View Integration Problems |
|
|
221 | (1) |
|
|
221 | (1) |
|
|
222 | (1) |
|
|
222 | (1) |
|
Supertype/Subtype Relationships |
|
|
222 | (1) |
|
A Final Step for Defining Relational Keys |
|
|
223 | (2) |
|
|
225 | (1) |
|
|
226 | (9) |
|
|
226 | (1) |
|
|
226 | (1) |
|
|
227 | (6) |
|
|
233 | (1) |
|
|
234 | (1) |
|
|
234 | (1) |
|
|
234 | (1) |
|
Case: Mountain View Community Hospital |
|
|
235 | (5) |
|
Physical Database Design and Performance |
|
|
240 | (49) |
|
|
240 | (1) |
|
|
240 | (1) |
|
Physical Database Design Process |
|
|
241 | (3) |
|
Data Volume and Usage Analysis |
|
|
242 | (2) |
|
|
244 | (4) |
|
|
244 | (1) |
|
Coding and Compression Techniques |
|
|
245 | (1) |
|
Controlling Data Integrity-A Foundation for Sarbanes-Oxley Compliance |
|
|
246 | (1) |
|
|
247 | (1) |
|
Designing Physical Records and Denormalization |
|
|
248 | (6) |
|
|
248 | (1) |
|
|
249 | (1) |
|
Opportunities and Types of Denormalization |
|
|
249 | (5) |
|
|
254 | (11) |
|
|
256 | (1) |
|
|
256 | (1) |
|
Sequential File Organizations |
|
|
256 | (1) |
|
Indexed File Organizations |
|
|
256 | (6) |
|
Hashed File Organizations |
|
|
262 | (1) |
|
Summary of File Organizations |
|
|
263 | (1) |
|
|
263 | (2) |
|
Designing Controls for Files |
|
|
265 | (1) |
|
Using and Selecting Indexes |
|
|
265 | (2) |
|
Creating a Unique Key Index |
|
|
265 | (1) |
|
Creating a Secondary (Nonunique) Key Index |
|
|
266 | (1) |
|
|
266 | (1) |
|
RAID: Improving File Access Performance by Parallel Processing |
|
|
267 | (3) |
|
|
270 | (3) |
|
Optimizing for Query Performance |
|
|
273 | (5) |
|
Parallel Query Processing |
|
|
273 | (1) |
|
Overriding Automatic Query Optimization |
|
|
274 | (1) |
|
|
275 | (1) |
|
Balancing I/O Across Disk Controllers |
|
|
275 | (1) |
|
Guidelines for Batter Query Design |
|
|
276 | (2) |
|
|
278 | (1) |
|
|
279 | (5) |
|
|
279 | (1) |
|
|
279 | (1) |
|
|
280 | (2) |
|
|
282 | (1) |
|
|
283 | (1) |
|
|
283 | (1) |
|
|
283 | (1) |
|
Case: Mountain View Community Hospital |
|
|
284 | (4) |
|
|
|
|
288 | (1) |
|
|
289 | (44) |
|
|
289 | (1) |
|
|
289 | (2) |
|
History of the SQL Standard |
|
|
291 | (1) |
|
The Role of SQL in a Database Architecture |
|
|
292 | (1) |
|
|
293 | (5) |
|
Defining a Database in SQL |
|
|
298 | (6) |
|
Generating SQL Database Definitions |
|
|
298 | (1) |
|
|
299 | (3) |
|
Creating Data Integrity Controls |
|
|
302 | (1) |
|
Changing Table Definitions |
|
|
302 | (2) |
|
|
304 | (1) |
|
Inserting, Updating, and Deleting Data |
|
|
304 | (3) |
|
|
305 | (1) |
|
Deleting Database Contents |
|
|
306 | (1) |
|
Updating Database Contents |
|
|
306 | (1) |
|
Internal Schema Definition in RDBMSs |
|
|
307 | (1) |
|
|
307 | (1) |
|
|
308 | (18) |
|
Clauses of the SELECT Statement |
|
|
309 | (1) |
|
|
310 | (1) |
|
|
311 | (1) |
|
|
312 | (1) |
|
Using Comparison Operators |
|
|
313 | (1) |
|
|
313 | (3) |
|
Using Ranges for Qualification |
|
|
316 | (1) |
|
|
317 | (1) |
|
Using IN and NOT IN with Lists |
|
|
318 | (1) |
|
Sorting Results: The ORDER BY Clause |
|
|
319 | (1) |
|
Categorizing Results: The GROUP BY Clause |
|
|
320 | (1) |
|
Qualifying Results by Categories: The HAVING Clause |
|
|
321 | (1) |
|
|
322 | (4) |
|
|
326 | (1) |
|
|
326 | (1) |
|
|
327 | (5) |
|
|
327 | (1) |
|
|
327 | (1) |
|
|
328 | (2) |
|
|
330 | (1) |
|
|
330 | (1) |
|
|
331 | (1) |
|
|
331 | (1) |
|
Case: Mountain View Community Hospital |
|
|
332 | (1) |
|
|
333 | (35) |
|
|
333 | (1) |
|
|
333 | (1) |
|
Processing Multiple Tables |
|
|
334 | (15) |
|
|
335 | (1) |
|
|
336 | (1) |
|
|
337 | (2) |
|
|
339 | (1) |
|
Sample Multiple Join Involving Four Tables |
|
|
339 | (1) |
|
|
340 | (3) |
|
|
343 | (2) |
|
|
345 | (1) |
|
|
346 | (1) |
|
|
347 | (1) |
|
More Complicated SQL Queries |
|
|
348 | (1) |
|
Ensuring Transaction Integrity |
|
|
349 | (1) |
|
Data Dictionary Facilities |
|
|
350 | (2) |
|
SQL:2003 Enhancements and Extensions to SQL |
|
|
352 | (4) |
|
|
352 | (2) |
|
|
354 | (1) |
|
|
354 | (1) |
|
|
355 | (1) |
|
|
356 | (4) |
|
|
357 | (1) |
|
|
358 | (2) |
|
Embedded SQL and Dynamic SQL |
|
|
360 | (2) |
|
|
362 | (1) |
|
|
363 | (4) |
|
|
363 | (1) |
|
|
363 | (1) |
|
|
364 | (1) |
|
|
364 | (1) |
|
|
365 | (1) |
|
|
366 | (1) |
|
|
366 | (1) |
|
Case: Mountain View Community Hospital |
|
|
367 | (1) |
|
The Client/Server Database Environment |
|
|
368 | (24) |
|
|
368 | (1) |
|
Location, Location, Location! |
|
|
368 | (1) |
|
|
369 | (1) |
|
Client/Server Architectures |
|
|
370 | (4) |
|
File Server Architectures |
|
|
371 | (1) |
|
Limitations of File Servers |
|
|
372 | (1) |
|
Database Server Architectures |
|
|
372 | (2) |
|
|
374 | (2) |
|
Partitioning an Application |
|
|
376 | (2) |
|
|
378 | (1) |
|
|
379 | (3) |
|
|
382 | (1) |
|
Using ODBC to Link External Tables Stored on a Database Server |
|
|
383 | (2) |
|
Using JDBC to Link External Tables Stored on a Database Server |
|
|
385 | (1) |
|
Looking Forward with Client/Server in Mind |
|
|
386 | (1) |
|
|
386 | (1) |
|
|
387 | (3) |
|
|
387 | (1) |
|
|
387 | (1) |
|
|
388 | (1) |
|
|
388 | (1) |
|
|
389 | (1) |
|
|
389 | (1) |
|
|
389 | (1) |
|
Case: Mountain View Community Hospital |
|
|
390 | (2) |
|
The Internet Database Environment |
|
|
392 | (28) |
|
|
392 | (1) |
|
|
392 | (1) |
|
The Internet and Database Connection |
|
|
393 | (1) |
|
|
394 | (2) |
|
Common Internet Architecture Components |
|
|
396 | (7) |
|
Internet-Related Languages |
|
|
396 | (1) |
|
|
397 | (2) |
|
|
399 | (1) |
|
|
400 | (1) |
|
|
401 | (1) |
|
|
402 | (1) |
|
|
403 | (11) |
|
|
405 | (6) |
|
|
411 | (1) |
|
|
412 | (1) |
|
Service-Oriented Architecture (SOA) |
|
|
412 | (1) |
|
|
413 | (1) |
|
Internet Technology Rate-of-Change Issues |
|
|
413 | (1) |
|
|
414 | (1) |
|
|
415 | (3) |
|
|
415 | (1) |
|
|
415 | (1) |
|
|
416 | (1) |
|
|
416 | (1) |
|
|
416 | (1) |
|
|
417 | (1) |
|
|
417 | (1) |
|
Case: Mountain View Community Hospital |
|
|
418 | (2) |
|
|
420 | (63) |
|
|
420 | (1) |
|
|
420 | (2) |
|
Basic Concepts of Data Warehousing |
|
|
422 | (6) |
|
|
423 | (1) |
|
The Need for Data Warehousing |
|
|
423 | (1) |
|
Need for a Companywide View |
|
|
423 | (3) |
|
Need to Separate Operational and Informational Systems |
|
|
426 | (1) |
|
|
426 | (2) |
|
Data Warehouse Architectures |
|
|
428 | (9) |
|
Generic Two-Level Architecture |
|
|
428 | (1) |
|
Independent Data Mart Data Warehousing Environment |
|
|
429 | (1) |
|
Dependent Data Mart and Operational Data Store Architecture: A Three-Level Approach |
|
|
430 | (2) |
|
Logical Data Mart and Real-Time Data Warehouse Archilecture |
|
|
432 | (3) |
|
Three-Layer Data Architecture |
|
|
435 | (1) |
|
Role of the Enterprise Data Model |
|
|
435 | (1) |
|
|
436 | (1) |
|
Some Characteristics of Data Warehouse Data |
|
|
437 | (4) |
|
|
437 | (1) |
|
Transient Versus Periodic Data |
|
|
438 | (1) |
|
An Example of Transient and Periodic Data |
|
|
438 | (1) |
|
|
438 | (1) |
|
|
439 | (1) |
|
Other Data Warehouse Changes |
|
|
440 | (1) |
|
The Reconciled Data Layer |
|
|
441 | (6) |
|
Characteristics of Data after ETL |
|
|
441 | (1) |
|
|
442 | (1) |
|
|
442 | (2) |
|
|
444 | (2) |
|
|
446 | (1) |
|
|
447 | (5) |
|
Data Transformation Functions |
|
|
448 | (1) |
|
|
448 | (1) |
|
|
449 | (2) |
|
More Complex Transformations |
|
|
451 | (1) |
|
Tools to Support Data Reconciliation |
|
|
451 | (1) |
|
|
451 | (1) |
|
|
452 | (1) |
|
|
452 | (1) |
|
|
452 | (1) |
|
|
452 | (13) |
|
Characteristics of Derived Data |
|
|
452 | (1) |
|
|
453 | (1) |
|
Fact Tables and Dimension Tables |
|
|
453 | (1) |
|
|
454 | (1) |
|
|
455 | (1) |
|
|
456 | (1) |
|
|
456 | (1) |
|
|
457 | (1) |
|
|
458 | (1) |
|
Variations of the Star Schema |
|
|
458 | (1) |
|
|
458 | (1) |
|
|
459 | (1) |
|
Normalizing Dimension Tables |
|
|
460 | (1) |
|
|
461 | (1) |
|
|
461 | (3) |
|
Slowly Changing Dimensions |
|
|
464 | (1) |
|
|
465 | (5) |
|
|
466 | (1) |
|
|
466 | (1) |
|
Online Analytical Processing (OLAP) Tools |
|
|
467 | (1) |
|
|
468 | (1) |
|
|
468 | (1) |
|
|
469 | (1) |
|
|
469 | (1) |
|
|
469 | (1) |
|
|
470 | (1) |
|
|
470 | (1) |
|
|
471 | (7) |
|
|
471 | (1) |
|
|
472 | (1) |
|
|
473 | (3) |
|
|
476 | (1) |
|
|
476 | (1) |
|
|
477 | (1) |
|
|
477 | (1) |
|
Case: Mountain View Community Hospital |
|
|
478 | (4) |
|
Part V Advanced Database Topics |
|
|
|
|
482 | (1) |
|
Data and Database Administration |
|
|
483 | (61) |
|
|
483 | (1) |
|
|
483 | (2) |
|
The Roles of Data and Database Administrators |
|
|
485 | (7) |
|
Traditional Data Administration |
|
|
485 | (2) |
|
Traditional Database Administration |
|
|
487 | (1) |
|
Evolving Approaches to Data Administration |
|
|
488 | (1) |
|
Blending Data and Database Administration |
|
|
488 | (2) |
|
|
490 | (1) |
|
|
490 | (2) |
|
|
492 | (1) |
|
|
492 | (2) |
|
|
494 | (1) |
|
|
494 | (1) |
|
Role of an Information Systems Architecture |
|
|
494 | (1) |
|
|
495 | (15) |
|
|
495 | (2) |
|
Establishing Client/Server Security |
|
|
497 | (1) |
|
|
497 | (1) |
|
|
497 | (1) |
|
Client/Server Security Issues for Web-Enabled Databases |
|
|
498 | (1) |
|
|
498 | (1) |
|
|
499 | (1) |
|
Database Software Data Security Features |
|
|
500 | (1) |
|
|
501 | (1) |
|
|
502 | (1) |
|
|
503 | (2) |
|
|
505 | (1) |
|
|
505 | (1) |
|
|
506 | (1) |
|
|
506 | (1) |
|
|
507 | (1) |
|
|
508 | (1) |
|
Security Policies and Procedures |
|
|
508 | (1) |
|
|
508 | (1) |
|
|
509 | (1) |
|
|
509 | (1) |
|
|
509 | (1) |
|
Database Backup and Recovery |
|
|
510 | (7) |
|
Basic Recovery Facilities |
|
|
510 | (1) |
|
|
510 | (1) |
|
|
511 | (1) |
|
|
511 | (1) |
|
|
512 | (1) |
|
Recovery and Restart Procedures |
|
|
512 | (1) |
|
|
512 | (1) |
|
|
512 | (1) |
|
Maintaining Transaction Integrity |
|
|
512 | (2) |
|
|
514 | (1) |
|
|
514 | (1) |
|
Types of Database Failure |
|
|
515 | (1) |
|
|
515 | (1) |
|
|
516 | (1) |
|
|
516 | (1) |
|
|
517 | (1) |
|
|
517 | (1) |
|
Controlling Concurrent Access |
|
|
517 | (6) |
|
The Problem of Lost Updates |
|
|
518 | (1) |
|
|
519 | (1) |
|
|
519 | (1) |
|
|
520 | (1) |
|
|
520 | (1) |
|
|
521 | (1) |
|
|
522 | (1) |
|
|
522 | (1) |
|
|
523 | (4) |
|
The State of Data Quality |
|
|
524 | (1) |
|
|
524 | (1) |
|
|
525 | (1) |
|
Lack of Organizational Commitment |
|
|
525 | (1) |
|
|
525 | (1) |
|
Conduct a Data Quality Audit |
|
|
525 | (1) |
|
Establish a Data Stewardship Program |
|
|
525 | (1) |
|
Apply TQM Principles and Practices |
|
|
526 | (1) |
|
Overcome Organizational Barriers |
|
|
526 | (1) |
|
Apply Modern Data Management Technology |
|
|
526 | (1) |
|
Estimate Return on Investment |
|
|
526 | (1) |
|
Data Dictionaries and Repositories |
|
|
527 | (2) |
|
|
527 | (1) |
|
|
528 | (1) |
|
Overview of Tuning the Database for Performance |
|
|
529 | (4) |
|
|
530 | (1) |
|
Memory and Storage Space Usage |
|
|
530 | (1) |
|
Input/Output (I/O) Contention |
|
|
531 | (1) |
|
|
531 | (1) |
|
|
532 | (1) |
|
|
533 | (2) |
|
|
533 | (1) |
|
Measures to Ensure Availability |
|
|
534 | (1) |
|
|
534 | (1) |
|
Loss or Corruption of Data |
|
|
534 | (1) |
|
|
534 | (1) |
|
|
534 | (1) |
|
|
535 | (1) |
|
|
535 | (7) |
|
|
535 | (1) |
|
|
536 | (1) |
|
|
537 | (2) |
|
|
539 | (1) |
|
|
540 | (1) |
|
|
540 | (1) |
|
|
541 | (1) |
|
Case: Mountain View Community Hospital |
|
|
542 | (2) |
|
Overview: Distributed Databases |
|
|
544 | (4) |
|
|
544 | (1) |
|
|
544 | (3) |
|
Objectives and Trade-Offs |
|
|
545 | (1) |
|
Options for Distributing a Database |
|
|
545 | (1) |
|
|
546 | (1) |
|
|
547 | (1) |
|
|
547 | (1) |
|
|
547 | (1) |
|
|
547 | (1) |
|
|
547 | (1) |
|
Overview: Object-Oriented Data Modeling |
|
|
548 | (8) |
|
|
548 | (1) |
|
|
548 | (7) |
|
The Unified Modeling Language |
|
|
549 | (1) |
|
Object-Oriented Data Modeling |
|
|
549 | (5) |
|
|
554 | (1) |
|
|
555 | (1) |
|
|
555 | (1) |
|
|
555 | (1) |
|
|
555 | (1) |
|
Overview: Object-Oriented Database Development |
|
|
556 | (6) |
|
|
556 | (1) |
|
|
556 | (5) |
|
Object Definition Language |
|
|
557 | (2) |
|
Creating Object Instances |
|
|
559 | (1) |
|
|
560 | (1) |
|
|
561 | (1) |
|
|
561 | (1) |
|
|
561 | (1) |
|
|
561 | (1) |
|
Appendix A Data Modeling Tools and Notation |
|
|
562 | (10) |
|
Comparing E-R Modeling Conventions |
|
|
562 | (9) |
|
Visio Professional 2003 Notation |
|
|
562 | (3) |
|
|
565 | (1) |
|
|
565 | (1) |
|
AllFusion ERwin Data Modeler 4.1 SP1 Notation |
|
|
565 | (1) |
|
|
565 | (1) |
|
|
565 | (3) |
|
Sybase Power Designer 11.1 Notation |
|
|
568 | (1) |
|
|
569 | (1) |
|
|
569 | (1) |
|
|
569 | (1) |
|
|
569 | (1) |
|
|
569 | (2) |
|
Comparison of Tool Interfaces and E-R Diagrams |
|
|
571 | (1) |
|
Appendix B Advanced Normal Forms |
|
|
572 | (6) |
|
|
572 | (2) |
|
Anomalies in STUDENT_ADVISOR |
|
|
573 | (1) |
|
Definition of Boyce-Codd Normal Form (BCNF) |
|
|
573 | (1) |
|
Converting a Relation to BCNF |
|
|
573 | (1) |
|
|
574 | (2) |
|
|
576 | (1) |
|
|
576 | (1) |
|
|
577 | (1) |
|
|
577 | (1) |
|
|
577 | (1) |
|
|
577 | (1) |
|
Appendix C Data Structures |
|
|
578 | (13) |
|
|
578 | (1) |
|
Data Structure Building Blocks |
|
|
579 | (2) |
|
|
581 | (5) |
|
|
582 | (1) |
|
|
583 | (1) |
|
|
583 | (2) |
|
|
585 | (1) |
|
Hazards of Chain Structures |
|
|
586 | (1) |
|
|
587 | (3) |
|
|
587 | (3) |
|
|
590 | (1) |
|
Appendix D Object-Relational Databases |
|
|
591 | (6) |
|
Basic Concepts and Definitions |
|
|
591 | (2) |
|
|
592 | (1) |
|
|
592 | (1) |
|
|
593 | (2) |
|
|
594 | (1) |
|
|
594 | (1) |
|
Advantages of the Object-Relational Approach |
|
|
595 | (1) |
|
ORDBMS Vendors and Products |
|
|
595 | (1) |
|
|
596 | (1) |
|
|
596 | (1) |
|
|
596 | (1) |
|
|
596 | (1) |
Glossary of Acronyms |
|
597 | (3) |
Glossary of Terms |
|
600 | (9) |
Index |
|
609 | |