Preface |
|
xxiii | |
|
Part I The Context of Database Management |
|
|
1 | (52) |
|
|
1 | (1) |
|
Chapter 1 The Database Environment and Development Process |
|
|
2 | (51) |
|
|
2 | (1) |
|
|
2 | (1) |
|
|
3 | (2) |
|
Basic Concepts and Definitions |
|
|
5 | (1) |
|
|
5 | (1) |
|
|
6 | (1) |
|
|
7 | (1) |
|
Traditional File Processing Systems |
|
|
8 | (1) |
|
File Processing Systems at Pine Valley Furniture Company |
|
|
8 | (1) |
|
Disadvantages of File Processing Systems |
|
|
8 | (1) |
|
|
8 | (1) |
|
|
9 | (1) |
|
|
9 | (1) |
|
Lengthy Development Times |
|
|
9 | (1) |
|
Excessive Program Maintenance |
|
|
9 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
Database Management Systems |
|
|
11 | (1) |
|
Advantages of the Database Approach |
|
|
12 | (1) |
|
Program-Data Independence |
|
|
13 | (1) |
|
|
13 | (1) |
|
Improved Data Consistency |
|
|
13 | (1) |
|
|
13 | (1) |
|
Increased Productivity of Application Development |
|
|
13 | (1) |
|
|
13 | (1) |
|
|
14 | (1) |
|
Improved Data Accessibility and Responsiveness |
|
|
14 | (1) |
|
Reduced Program Maintenance |
|
|
14 | (1) |
|
Improved Decision Support |
|
|
15 | (1) |
|
Cautions About Database Benefits |
|
|
15 | (1) |
|
Costs and Risks of the Database Approach |
|
|
15 | (1) |
|
New, Specialized Personnel |
|
|
15 | (1) |
|
Installation and Management Cost and Complexity |
|
|
15 | (1) |
|
|
15 | (1) |
|
Need for Explicit Backup and Recovery |
|
|
15 | (1) |
|
|
16 | (1) |
|
Components of the Database Environment |
|
|
16 | (1) |
|
The Database Development Process |
|
|
17 | (1) |
|
Systems Development Life Cycle |
|
|
18 | (1) |
|
Planning---Enterprise Modeling |
|
|
19 | (1) |
|
Planning---Conceptual Data Modeling |
|
|
19 | (1) |
|
Analysis---Conceptual Data Modeling |
|
|
20 | (1) |
|
Design---Logical Database Design |
|
|
20 | (1) |
|
Design---Physical Database Design and Definition |
|
|
20 | (1) |
|
Implementation---Database Implementation |
|
|
21 | (1) |
|
Maintenance---Database Maintenance |
|
|
21 | (1) |
|
Alternative Information Systems (IS) Development Approaches |
|
|
21 | (2) |
|
Three-Schema Architecture for Database Development |
|
|
23 | (1) |
|
Managing the People Involved in Database Development |
|
|
23 | (2) |
|
Evolution of Database Systems |
|
|
25 | (1) |
|
|
25 | (2) |
|
|
27 | (1) |
|
|
27 | (1) |
|
|
27 | (1) |
|
|
27 | (1) |
|
The Range of Database Applications |
|
|
28 | (1) |
|
|
28 | (1) |
|
Two-Tier Client/Server Databases |
|
|
29 | (1) |
|
Multitier Client/Server Databases |
|
|
29 | (1) |
|
|
30 | (1) |
|
Developing a Database Application for Pine Valley Furniture Company |
|
|
31 | (2) |
|
Database Evolution at Pine Valley Furniture Company |
|
|
33 | (1) |
|
|
33 | (1) |
|
Analyzing Database Requirements |
|
|
34 | (2) |
|
|
36 | (3) |
|
|
39 | (2) |
|
Administering the Database |
|
|
41 | (1) |
|
Future of Databases at Pine Valley |
|
|
41 | (12) |
|
|
41 | (1) |
|
|
42 | (1) |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
|
46 | (1) |
|
|
47 | (1) |
|
Case: Mountain View Community Hospital |
|
|
48 | (5) |
|
Part II Database Analysis |
|
|
53 | (98) |
|
|
53 | (2) |
|
Chapter 2 Modeling Data in the Organization |
|
|
55 | (57) |
|
|
55 | (1) |
|
|
55 | (2) |
|
The E-R Model: An Overview |
|
|
57 | (1) |
|
|
57 | (2) |
|
|
59 | (1) |
|
Modeling the Rules of the Organization |
|
|
60 | (1) |
|
Overview of Business Rules |
|
|
61 | (1) |
|
The Business Rules Paradigm |
|
|
61 | (1) |
|
|
62 | (1) |
|
|
62 | (1) |
|
|
63 | (1) |
|
Data Names and Definitions |
|
|
63 | (1) |
|
|
63 | (1) |
|
|
64 | (1) |
|
|
64 | (2) |
|
Modeling Entities and Attributes |
|
|
66 | (1) |
|
|
66 | (1) |
|
Entity Type Versus Entity Instance |
|
|
66 | (1) |
|
Entity Type Versus System Input, Output, or User |
|
|
66 | (1) |
|
Strong Versus Weak Entity Types |
|
|
67 | (1) |
|
Naming and Defining Entity Types |
|
|
68 | (2) |
|
|
70 | (1) |
|
Required Versus Optional Attributes |
|
|
70 | (1) |
|
Simple Versus Composite Attributes |
|
|
71 | (1) |
|
Single-Valued Versus Multivalued Attributes |
|
|
71 | (1) |
|
Stored Versus Derived Attributes |
|
|
72 | (1) |
|
|
72 | (1) |
|
Naming and Defining Attributes |
|
|
73 | (2) |
|
|
75 | (1) |
|
Basic Concepts and Definitions in Relationships |
|
|
76 | (1) |
|
Attributes on Relationships |
|
|
77 | (1) |
|
|
77 | (2) |
|
|
79 | (1) |
|
|
79 | (2) |
|
|
81 | (1) |
|
|
82 | (1) |
|
|
83 | (2) |
|
|
85 | (1) |
|
|
85 | (1) |
|
|
85 | (1) |
|
Some Examples of Relationships and Their Cardinalities |
|
|
86 | (1) |
|
|
87 | (1) |
|
Modeling Time-Dependent Data |
|
|
87 | (3) |
|
Modeling Multiple Relationships Between Entity Types |
|
|
90 | (2) |
|
Naming and Defining Relationships |
|
|
92 | (1) |
|
E-R Modeling Example: Pine Valley Furniture Company |
|
|
93 | (3) |
|
Database Processing at Pine Valley Furniture |
|
|
96 | (1) |
|
Showing Product Information |
|
|
96 | (1) |
|
Showing Product Line Information |
|
|
97 | (1) |
|
Showing Customer Order Status |
|
|
97 | (1) |
|
|
98 | (14) |
|
|
99 | (1) |
|
|
100 | (1) |
|
|
100 | (1) |
|
|
101 | (7) |
|
|
108 | (1) |
|
|
109 | (1) |
|
|
109 | (1) |
|
|
109 | (1) |
|
Case: Mountain View Community Hospital |
|
|
110 | (2) |
|
Chapter 3 The Enhanced E-R Model |
|
|
112 | (39) |
|
|
112 | (1) |
|
|
112 | (1) |
|
Representing Supertypes and Subtypes |
|
|
113 | (1) |
|
Basic Concepts and Notation |
|
|
114 | (1) |
|
An Example of a Supertype/Subtype Relationship |
|
|
115 | (1) |
|
|
116 | (1) |
|
When to Use Supertype/Subtype Relationships |
|
|
116 | (1) |
|
Representing Specialization and Generalization |
|
|
117 | (1) |
|
|
117 | (2) |
|
|
119 | (1) |
|
Combining Specialization and Generalization |
|
|
120 | (1) |
|
Specifying Constraints in Supertype/Subtype Relationships |
|
|
120 | (1) |
|
Specifying Completeness Constraints |
|
|
120 | (1) |
|
Total Specialization Rule |
|
|
120 | (1) |
|
Partial Specialization Rule |
|
|
121 | (1) |
|
Specifying Disjointness Constraints |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
122 | (1) |
|
Defining Subtype Discriminators |
|
|
122 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
Defining Supertype/Subtype Hierarchies |
|
|
124 | (1) |
|
An Example of a Supertype/Subtype Hierarchy |
|
|
124 | (1) |
|
Summary of Supertype/Subtype Hierarchies |
|
|
125 | (1) |
|
EER Modeling Example: Pine Valley Furniture Company |
|
|
126 | (3) |
|
|
129 | (3) |
|
|
132 | (2) |
|
A Revised Data Modeling Process with Packaged Data Models |
|
|
134 | (2) |
|
Packaged Data Model Examples |
|
|
136 | (15) |
|
|
141 | (1) |
|
|
142 | (1) |
|
|
142 | (1) |
|
|
143 | (3) |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
147 | (1) |
|
Case: Mountain View Community Hospital |
|
|
148 | (3) |
|
|
151 | (90) |
|
An Overview of Part Three |
|
|
151 | (2) |
|
Chapter 4 Logical Database Design and the Relational Model |
|
|
153 | (53) |
|
|
153 | (1) |
|
|
153 | (1) |
|
The Relational Data Model |
|
|
154 | (1) |
|
|
154 | (1) |
|
Relational Data Structure |
|
|
155 | (1) |
|
|
155 | (1) |
|
|
156 | (1) |
|
Removing Multivalued Attributes from Tables |
|
|
156 | (1) |
|
|
156 | (2) |
|
|
158 | (1) |
|
|
158 | (1) |
|
|
158 | (2) |
|
|
160 | (1) |
|
Creating Relational Tables |
|
|
161 | (1) |
|
Well-Structured Relations |
|
|
162 | (1) |
|
Transforming EER Diagrams into Relations |
|
|
163 | (1) |
|
Step 1: Map Regular Entities |
|
|
164 | (1) |
|
|
164 | (1) |
|
|
165 | (1) |
|
Step 2: Map Weak Entities |
|
|
165 | (1) |
|
When to Create a Surrogate Key |
|
|
166 | (1) |
|
Step 3: Map Binary Relationships |
|
|
167 | (1) |
|
Map Binary One-to-Many Relationships |
|
|
167 | (1) |
|
Map Binary Many-to-Many Relationships |
|
|
167 | (1) |
|
Map Binary One-to-One Relationships |
|
|
168 | (1) |
|
Step 4: Map Associative Entities |
|
|
169 | (1) |
|
|
169 | (1) |
|
|
170 | (1) |
|
Step 5: Map Unary Relationships |
|
|
171 | (1) |
|
Unary One-to-Many Relationships |
|
|
171 | (1) |
|
Unary Many-to-Many Relationships |
|
|
171 | (2) |
|
Step 6: Map Ternary (and n-ary) Relationships |
|
|
173 | (1) |
|
Step 7: Map Supertype/Subtype Relationships |
|
|
173 | (2) |
|
Summary of EER-to-Relational Transformations |
|
|
175 | (1) |
|
Introduction to Normalization |
|
|
176 | (1) |
|
|
177 | (1) |
|
Functional Dependencies and Keys |
|
|
178 | (1) |
|
|
178 | (1) |
|
|
178 | (2) |
|
Normalization Example: Pine Valley Furniture Company |
|
|
180 | (1) |
|
Step 0: Represent the View in Tabular Form |
|
|
180 | (1) |
|
Step 1: Convert to First Normal Form |
|
|
181 | (1) |
|
|
181 | (1) |
|
|
181 | (1) |
|
|
182 | (1) |
|
Step 2: Convert to Second Normal Form |
|
|
182 | (1) |
|
Step 3: Convert to Third Normal Form |
|
|
183 | (1) |
|
Removing Transitive Dependencies |
|
|
184 | (1) |
|
Determinants and Normalization |
|
|
185 | (1) |
|
Step 4: Further Normalization |
|
|
185 | (1) |
|
|
185 | (1) |
|
|
186 | (1) |
|
View Integration Problems |
|
|
186 | (1) |
|
|
186 | (1) |
|
|
187 | (1) |
|
|
187 | (1) |
|
Supertype/Subtype Relationships |
|
|
188 | (1) |
|
A Final Step for Defining Relational Keys |
|
|
188 | (18) |
|
|
190 | (2) |
|
|
192 | (1) |
|
|
192 | (1) |
|
|
193 | (7) |
|
|
200 | (1) |
|
|
200 | (1) |
|
|
201 | (1) |
|
|
201 | (1) |
|
Case: Mountain View Community Hospital |
|
|
202 | (4) |
|
Chapter 5 Physical Database Design and Performance |
|
|
206 | (35) |
|
|
206 | (1) |
|
|
206 | (1) |
|
The Physical Database Design Process |
|
|
207 | (1) |
|
Physical Database Design as a Basis for Regulatory Compliance |
|
|
208 | (1) |
|
Data Volume and Usage Analysis |
|
|
209 | (1) |
|
|
210 | (1) |
|
|
211 | (1) |
|
|
212 | (1) |
|
|
213 | (1) |
|
Denormalizing and Partitioning Data |
|
|
213 | (1) |
|
|
213 | (1) |
|
Opportunities for and Types of Denormalization |
|
|
214 | (2) |
|
|
216 | (1) |
|
|
217 | (2) |
|
Designing Physical Database Files |
|
|
219 | (1) |
|
|
220 | (1) |
|
Sequential File Organizations |
|
|
221 | (1) |
|
Indexed File Organizations |
|
|
221 | (3) |
|
Hashed File Organizations |
|
|
224 | (2) |
|
|
226 | (1) |
|
Designing Controls for Files |
|
|
227 | (1) |
|
Using and Selecting Indexes |
|
|
228 | (1) |
|
Creating a Unique Key Index |
|
|
228 | (1) |
|
Creating a Secondary (Nonunique) Key Index |
|
|
228 | (1) |
|
|
229 | (1) |
|
Designing a Database for Optimal Query Performance |
|
|
230 | (1) |
|
Parallel Query Processing |
|
|
230 | (1) |
|
Overriding Automatic Query Optimization |
|
|
231 | (10) |
|
|
232 | (1) |
|
|
233 | (1) |
|
|
233 | (1) |
|
|
233 | (3) |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
237 | (1) |
|
|
237 | (1) |
|
Case: Mountain View Community Hospital |
|
|
238 | (3) |
|
|
241 | (192) |
|
|
241 | (2) |
|
Chapter 6 Introduction to SQL |
|
|
243 | (46) |
|
|
243 | (1) |
|
|
243 | (2) |
|
Origins of the SQL Standard |
|
|
245 | (1) |
|
|
246 | (5) |
|
Defining a Database in SQL |
|
|
251 | (1) |
|
Generating SQL Database Definitions |
|
|
252 | (1) |
|
|
252 | (3) |
|
Creating Data Integrity Controls |
|
|
255 | (1) |
|
Changing Table Definitions |
|
|
256 | (1) |
|
|
257 | (1) |
|
Inserting, Updating, and Deleting Data |
|
|
257 | (1) |
|
|
258 | (1) |
|
Deleting Database Contents |
|
|
259 | (1) |
|
Updating Database Contents |
|
|
259 | (1) |
|
Internal Schema Definition in RDBMSs |
|
|
260 | (1) |
|
|
260 | (1) |
|
|
261 | (1) |
|
Clauses of the Select Statement |
|
|
261 | (2) |
|
|
263 | (1) |
|
|
264 | (3) |
|
|
267 | (1) |
|
Using Comparison Operators |
|
|
267 | (1) |
|
|
268 | (1) |
|
|
268 | (2) |
|
Using Ranges for Qualification |
|
|
270 | (1) |
|
|
271 | (2) |
|
Using In and Not In with Lists |
|
|
273 | (1) |
|
Sorting Results: The Order By Clause |
|
|
273 | (1) |
|
Categorizing Results: The Group By Clause |
|
|
274 | (1) |
|
Qualifying Results by Categories: The Having Clause |
|
|
275 | (2) |
|
|
277 | (4) |
|
|
281 | (8) |
|
|
281 | (1) |
|
|
282 | (1) |
|
|
282 | (1) |
|
|
283 | (3) |
|
|
286 | (1) |
|
|
286 | (1) |
|
|
287 | (1) |
|
|
287 | (1) |
|
Case: Mountain View Community Hospital |
|
|
288 | (1) |
|
|
289 | (47) |
|
|
289 | (1) |
|
|
289 | (1) |
|
Processing Multiple Tables |
|
|
290 | (1) |
|
|
291 | (1) |
|
|
292 | (1) |
|
|
293 | (2) |
|
Sample Join Involving Four Tables |
|
|
295 | (2) |
|
|
297 | (1) |
|
|
298 | (5) |
|
|
303 | (2) |
|
|
305 | (1) |
|
|
306 | (2) |
|
|
308 | (1) |
|
More Complicated SQL Queries |
|
|
308 | (2) |
|
Tips for Developing Queries |
|
|
310 | (2) |
|
Guidelines for Better Query Design |
|
|
312 | (2) |
|
Ensuring Transaction Integrity |
|
|
314 | (1) |
|
Data Dictionary Facilities |
|
|
315 | (2) |
|
SQL:2008 Enhancements and Extensions to SQL |
|
|
317 | (1) |
|
Analytical and OLAP Functions |
|
|
317 | (2) |
|
|
319 | (1) |
|
|
319 | (1) |
|
|
320 | (1) |
|
|
321 | (1) |
|
|
322 | (2) |
|
|
324 | (1) |
|
Example Routine in Oracle's PL/SQL |
|
|
325 | (2) |
|
Embedded SQL and Dynamic SQL |
|
|
327 | (9) |
|
|
329 | (1) |
|
|
330 | (1) |
|
|
330 | (1) |
|
|
331 | (3) |
|
|
334 | (1) |
|
|
334 | (1) |
|
|
334 | (1) |
|
|
334 | (1) |
|
Case: Mountain View Community Hospital |
|
|
335 | (1) |
|
Chapter 8 Database Application Development |
|
|
336 | (39) |
|
|
336 | (1) |
|
Location, Location, Location! |
|
|
336 | (1) |
|
|
337 | (1) |
|
Client/Server Architectures |
|
|
337 | (2) |
|
Databases in a Two-Tier Architecture |
|
|
339 | (2) |
|
|
341 | (2) |
|
|
343 | (1) |
|
|
344 | (2) |
|
Web Application Components |
|
|
346 | (2) |
|
Databases in Three-Tier Applications |
|
|
348 | (1) |
|
|
348 | (4) |
|
|
352 | (1) |
|
|
352 | (2) |
|
Key Considerations in Three-Tier Applications |
|
|
354 | (1) |
|
|
355 | (1) |
|
|
356 | (2) |
|
|
358 | (1) |
|
Key Benefits of Three-Tier Applications |
|
|
358 | (1) |
|
Cloud Computing and Three-Tier Applications |
|
|
359 | (1) |
|
Extensible Markup Language (XML) |
|
|
360 | (2) |
|
|
362 | (1) |
|
|
362 | (3) |
|
|
365 | (1) |
|
|
365 | (10) |
|
|
369 | (1) |
|
|
369 | (1) |
|
|
370 | (1) |
|
|
370 | (1) |
|
|
371 | (1) |
|
|
371 | (1) |
|
|
371 | (1) |
|
|
371 | (2) |
|
Case: Mountain View Community Hospital |
|
|
373 | (2) |
|
Chapter 9 Data Warehousing |
|
|
375 | (58) |
|
|
375 | (1) |
|
|
375 | (2) |
|
Basic Concepts of Data Warehousing |
|
|
377 | (1) |
|
A Brief History of Data Warehousing |
|
|
377 | (1) |
|
The Need for Data Warehousing |
|
|
377 | (1) |
|
Need For a Company-Wide View |
|
|
378 | (3) |
|
Need to Separate Operational and Informational Systems |
|
|
381 | (1) |
|
Data Warehouse Architectures |
|
|
381 | (1) |
|
Independent Data Mart Data Warehousing Environment |
|
|
381 | (2) |
|
Dependent Data Mart and Operational Data Store Architecture: A Three-Level Approach |
|
|
383 | (2) |
|
Logical Data Mart and Real-Time Data Warehouse Architecture |
|
|
385 | (3) |
|
Three-Layer Data Architecture |
|
|
388 | (1) |
|
Role of the Enterprise Data Model |
|
|
389 | (1) |
|
|
389 | (1) |
|
Some Characteristics of Data Warehouse Data |
|
|
389 | (1) |
|
|
389 | (1) |
|
Transient Versus Periodic Data |
|
|
390 | (1) |
|
An Example of Transient and Periodic Data |
|
|
390 | (1) |
|
|
390 | (2) |
|
|
392 | (1) |
|
Other Data Warehouse Changes |
|
|
392 | (1) |
|
|
393 | (1) |
|
Characteristics of Derived Data |
|
|
393 | (1) |
|
|
394 | (1) |
|
Fact Tables and Dimension Tables |
|
|
394 | (1) |
|
|
395 | (2) |
|
|
397 | (1) |
|
|
397 | (1) |
|
|
398 | (1) |
|
|
398 | (1) |
|
|
399 | (1) |
|
Variations of the Star Schema |
|
|
400 | (1) |
|
|
400 | (1) |
|
|
401 | (1) |
|
Normalizing Dimension Tables |
|
|
401 | (1) |
|
|
402 | (1) |
|
|
403 | (2) |
|
Slowly Changing Dimensions |
|
|
405 | (3) |
|
Determining Dimensions and Facts |
|
|
408 | (1) |
|
Big Data and Colunnar Databases |
|
|
408 | (3) |
|
If You Knew SQL Like 1 NoSQL |
|
|
411 | (1) |
|
|
412 | (1) |
|
|
412 | (1) |
|
|
413 | (2) |
|
Online Analytical Processing (OLAP) Tools |
|
|
415 | (1) |
|
|
416 | (1) |
|
|
416 | (1) |
|
Summarizing More than Three Dimensions |
|
|
417 | (1) |
|
|
417 | (1) |
|
Business Performance Management and Dashboards |
|
|
418 | (1) |
|
|
419 | (1) |
|
|
419 | (1) |
|
|
420 | (13) |
|
|
421 | (1) |
|
|
421 | (1) |
|
|
422 | (1) |
|
|
422 | (4) |
|
|
426 | (1) |
|
|
427 | (1) |
|
|
427 | (1) |
|
|
427 | (2) |
|
Case: Mountain View Community Hospital |
|
|
429 | (4) |
|
Part V Advanced Database Topics |
|
|
433 | (133) |
|
|
433 | (2) |
|
Chapter 10 Data Quality and Integration |
|
|
435 | (28) |
|
|
435 | (1) |
|
|
435 | (1) |
|
|
436 | (1) |
|
|
437 | (1) |
|
Characteristics of Quality Data |
|
|
438 | (1) |
|
|
439 | (1) |
|
Redundant Data Storage and Inconsistent Metadata |
|
|
440 | (1) |
|
|
440 | (1) |
|
Lack of Organizational Commitment |
|
|
440 | (1) |
|
|
440 | (1) |
|
|
440 | (1) |
|
Conduct a Data Quality Audit |
|
|
441 | (1) |
|
Establish a Data Stewardship Program |
|
|
442 | (1) |
|
Improve Data Capture Processes |
|
|
442 | (1) |
|
Apply Modern Data Management Principles and Technology |
|
|
443 | (1) |
|
Apply TQM Principles and Practices |
|
|
443 | (1) |
|
|
443 | (1) |
|
|
444 | (1) |
|
Data Integration: An Overview |
|
|
445 | (1) |
|
General Approaches to Data Integration |
|
|
445 | (1) |
|
|
446 | (1) |
|
|
447 | (1) |
|
Data Integration for Data Warehousing: The Reconciled Data Layer |
|
|
447 | (1) |
|
Characteristics of Data After ETL |
|
|
447 | (1) |
|
|
448 | (1) |
|
Mapping and Metadata Management |
|
|
448 | (1) |
|
|
449 | (1) |
|
|
450 | (2) |
|
|
452 | (1) |
|
|
453 | (1) |
|
Data Transformation Functions |
|
|
454 | (1) |
|
|
454 | (1) |
|
|
455 | (8) |
|
|
457 | (1) |
|
|
457 | (1) |
|
|
457 | (1) |
|
|
458 | (1) |
|
|
459 | (1) |
|
|
459 | (1) |
|
|
460 | (1) |
|
|
460 | (1) |
|
Case: Mountain View Community Hospital |
|
|
461 | (2) |
|
Chapter 11 Data and Database Administration |
|
|
463 | (50) |
|
|
463 | (1) |
|
|
463 | (1) |
|
The Roles of Data and Database Administrators |
|
|
464 | (1) |
|
Traditional Data Administration |
|
|
465 | (1) |
|
Traditional Database Administration |
|
|
466 | (3) |
|
Trends in Database Administration |
|
|
469 | (1) |
|
Data Warehouse Administration |
|
|
470 | (1) |
|
Summary of Evolving Data Administration Roles |
|
|
470 | (1) |
|
The Open Source Movement and Database Management |
|
|
471 | (1) |
|
|
472 | (1) |
|
|
473 | (1) |
|
Establishing Client/Server Security |
|
|
474 | (1) |
|
|
474 | (1) |
|
|
475 | (1) |
|
Application Security Issues in Three-Tier Client/Server Environments |
|
|
475 | (1) |
|
|
476 | (1) |
|
Database Software Data Security Features |
|
|
477 | (1) |
|
|
478 | (1) |
|
|
479 | (1) |
|
|
480 | (2) |
|
|
482 | (1) |
|
|
482 | (1) |
|
|
483 | (1) |
|
|
483 | (1) |
|
|
483 | (1) |
|
Sarbanes-Oxley (SOX) and Databases |
|
|
484 | (1) |
|
|
484 | (1) |
|
|
484 | (1) |
|
|
485 | (1) |
|
|
485 | (1) |
|
|
485 | (1) |
|
Database Backup and Recovery |
|
|
486 | (1) |
|
Basic Recovery Facilities |
|
|
486 | (1) |
|
|
486 | (1) |
|
|
487 | (1) |
|
|
487 | (1) |
|
|
488 | (1) |
|
Recovery and Restart Procedures |
|
|
488 | (1) |
|
|
488 | (1) |
|
|
488 | (1) |
|
Maintaining Transaction Integrity |
|
|
488 | (2) |
|
|
490 | (1) |
|
|
490 | (1) |
|
Types of Database Failure |
|
|
491 | (1) |
|
|
492 | (1) |
|
|
492 | (1) |
|
|
492 | (1) |
|
|
492 | (1) |
|
|
493 | (1) |
|
Controlling Concurrent Access |
|
|
493 | (1) |
|
The Problem of Lost Updates |
|
|
493 | (1) |
|
|
494 | (1) |
|
|
494 | (1) |
|
|
495 | (1) |
|
|
496 | (1) |
|
|
496 | (1) |
|
|
497 | (1) |
|
|
498 | (1) |
|
Data Dictionaries and Repositories |
|
|
499 | (1) |
|
|
499 | (1) |
|
|
499 | (2) |
|
Overview of Tuning the Database for Performance |
|
|
501 | (1) |
|
|
501 | (1) |
|
Memory and Storage Space Usage |
|
|
502 | (1) |
|
Input/Output (I/O) Contention |
|
|
502 | (1) |
|
|
503 | (1) |
|
|
503 | (1) |
|
|
504 | (1) |
|
|
504 | (1) |
|
Measures to Ensure Availability |
|
|
505 | (1) |
|
|
505 | (1) |
|
Loss or Corruption of Data |
|
|
505 | (1) |
|
|
505 | (1) |
|
|
505 | (1) |
|
|
506 | (7) |
|
|
506 | (1) |
|
|
507 | (1) |
|
|
507 | (1) |
|
|
508 | (2) |
|
|
510 | (1) |
|
|
511 | (1) |
|
|
511 | (1) |
|
|
511 | (1) |
|
Case: Mountain View Community Hospital |
|
|
512 | (1) |
|
Chapter 12 Overview: Distributed Databases |
|
|
513 | (5) |
|
|
513 | (1) |
|
|
513 | (1) |
|
Objectives and Trade-offs |
|
|
514 | (1) |
|
Options for Distributing a Database |
|
|
514 | (1) |
|
|
515 | (1) |
|
|
515 | (2) |
|
|
516 | (1) |
|
|
517 | (1) |
|
|
517 | (1) |
|
|
517 | (1) |
|
|
517 | (1) |
|
Chapter 13 Overview: Object-Oriented Data Modeling |
|
|
518 | (10) |
|
|
518 | (1) |
|
|
518 | (1) |
|
Unified Modeling Language |
|
|
519 | (1) |
|
Object-Oriented Data Modeling |
|
|
519 | (6) |
|
|
525 | (1) |
|
|
525 | (1) |
|
|
526 | (2) |
|
|
526 | (1) |
|
|
527 | (1) |
|
|
527 | (1) |
|
Chapter 14 Overview: Using Relational Databases to Provide Object Persistence |
|
|
528 | (38) |
|
|
528 | (1) |
|
|
528 | (1) |
|
Providing Persistence for Objects Using Relational Databases |
|
|
529 | (1) |
|
Call-Level Application Programming Interfaces |
|
|
529 | (1) |
|
SQL Query Mapping Frameworks |
|
|
530 | (1) |
|
Object-Relational Mapping Frameworks |
|
|
530 | (1) |
|
|
530 | (1) |
|
Selecting the Right Approach |
|
|
530 | (1) |
|
Object-Relational Mapping Example |
|
|
531 | (1) |
|
|
532 | (3) |
|
Responsibilities of Object-Relational Mapping Frameworks |
|
|
535 | (1) |
|
|
536 | (1) |
|
|
536 | (2) |
|
|
536 | (1) |
|
|
537 | (1) |
|
|
537 | (1) |
|
Appendix A Data Modeling Tools and Notation |
|
|
538 | (1) |
|
Comparing E-R Modeling Conventions |
|
|
538 | (1) |
|
Visio Professional 2010 Notation |
|
|
538 | (4) |
|
|
542 | (1) |
|
|
542 | (1) |
|
CA ERwin Data Modeler r8 Notation |
|
|
542 | (1) |
|
|
542 | (1) |
|
|
542 | (2) |
|
Sybase PowerDesigner 16 Notation |
|
|
544 | (1) |
|
|
545 | (1) |
|
|
545 | (1) |
|
|
545 | (1) |
|
|
545 | (1) |
|
|
545 | (1) |
|
Comparison of Tool Interfaces and E-R Diagrams |
|
|
545 | (3) |
|
Appendix B Advanced Normal Forms |
|
|
548 | (1) |
|
|
548 | (1) |
|
Anomalies in Student Advisor |
|
|
548 | (1) |
|
Definition of Boyce-Codd Normal Form (BCNF) |
|
|
549 | (1) |
|
Converting a Relation to BCNF |
|
|
549 | (1) |
|
|
550 | (2) |
|
|
552 | (1) |
|
|
552 | (2) |
|
|
553 | (1) |
|
|
553 | (1) |
|
|
553 | (1) |
|
Appendix C Data Structures |
|
|
554 | (1) |
|
|
554 | (1) |
|
Data Structure Building Blocks |
|
|
555 | (2) |
|
|
557 | (1) |
|
|
558 | (1) |
|
|
558 | (1) |
|
|
559 | (2) |
|
|
561 | (1) |
|
Hazards of Chain Structures |
|
|
561 | (1) |
|
|
562 | (1) |
|
|
562 | (3) |
|
|
565 | (1) |
Glossary of Acronyms |
|
566 | (2) |
Glossary of Terms |
|
568 | (8) |
Index |
|
576 | |