ebook download (eBook PDF) Database Processing Fundamentals, Design, and Implementation, 15th Edition all chapter

(eBook PDF) Database Processing
Fundamentals, Design, and

Implementation, 15th Edition
Go to download the full and correct content document:
https://ebooksecure.com/product/ebook-pdf-database-processing-fundamentals-desig
n-and-implementation-15th-edition/
More products digital (pdf, epub, mobi) instant
download maybe you interests ...
(Original PDF) Database Processing: Fundamentals,

Design, and Implementation 14th
http://ebooksecure.com/product/original-pdf-database-processing-
fundamentals-design-and-implementation-14th/
Database Processing: Fundamentals, Design, and

Implementation 16th Edition David M. Kroenke - eBook
PDF
https://ebooksecure.com/download/database-processing-
fundamentals-design-and-implementation-ebook-pdf/
Database Principles: Fundamentals of Design,

Implementation, and Management 3rd Edition Carlos
Coronel - eBook PDF
https://ebooksecure.com/download/database-principles-
fundamentals-of-design-implementation-and-management-ebook-pdf/
Database Systems: Design, Implementation, Management

11th Edition (eBook PDF)
http://ebooksecure.com/product/database-systems-design-
implementation-management-11th-edition-ebook-pdf/
(eBook PDF) Database Systems Design, Implementation, &
Management 13th Edition
http://ebooksecure.com/product/ebook-pdf-database-systems-design-
implementation-management-13th-edition/
Database Systems: Design, Implementation, & Management

13th Edition (eBook PDF)
http://ebooksecure.com/product/database-systems-design-
implementation-management-13th-edition-ebook-pdf/
(eBook PDF) Materials: Engineering, Science, Processing

and Design 4th Edition
http://ebooksecure.com/product/ebook-pdf-materials-engineering-
science-processing-and-design-4th-edition/
(eBook PDF) Operations Strategy: Design, Implementation

and Delivery 1st ed. 2018 Edition
http://ebooksecure.com/product/ebook-pdf-operations-strategy-
design-implementation-and-delivery-1st-ed-2018-edition/
(eBook PDF) Database Design Application Development

Administration 7th by Mannino
http://ebooksecure.com/product/ebook-pdf-database-design-
application-development-administration-7th-by-mannino/
Kroenke 40th Anniversary Edition
Auer
Vandenberg
Yoder
D ATA B A S E P R O C E S S I N G
FUNDAMENTALS, DESIGN, AND IMPLEMENTATION
D ATA B A S E P R O C E S S I N G
FUNDAMENTALS, DESIGN, AND IMPLEMENTATION
FIFTEENTH
David M. Kroenke David J. Auer Scott L. Vandenberg Robert C. Yoder
www.pearson.com
EDITION
FIFTEENTH EDITION
vi Contents
SQL Enhancements for Querying a Single Table 66

Reading Specified Rows from a Single Table 66 • Reading Specified Columns and Rows from a
Single Table 70 • Sorting the SQL Query Results 70 • SQL WHERE Clause Options 73
Performing Calculations in SQL Queries 80
Using SQL Built-in Aggregate Functions 81 • SQL Expressions in SQL SELECT Statements 85
Grouping Rows in SQL SELECT Statements 88
Querying Two or More Tables with SQL 93
Querying Multiple Tables with Subqueries 93 • Querying Multiple Tables with Joins 96
• Comparing Subqueries and Joins 102 • The SQL JOIN ON Syntax 102 • SQL Queries
on Recursive Relationships 106 • Outer Joins 107 • Using SQL Set Operators 111
Summary 115 • Key Terms 116 • Review Questions 117 • Exercises 124
• Case Questions 129 • The Queen Anne Curiosity Shop Project Questions 133
• Morgan Importing Project Questions 140
PART 2 ■ Database Design 145
Chapter 3: The Relational Model and Normalization 146

Chapter Objectives 146
Relational Model Terminology 148
Relations 148 • Characteristics of Relations 149 • Alternative Terminology 151
• To Key, or Not to Key—That Is the Question! 152 • Functional Dependencies 152
• Finding Functional Dependencies 154 • Keys 157
Normal Forms 161
Modification Anomalies 161 • A Short History of Normal Forms 162 • Normalization
Categories 163 • From First Normal Form to Boyce-Codd Normal Form Step by Step 164
• Eliminating Anomalies from Functional Dependencies with BCNF 167 • Eliminating
Anomalies from Multivalued Dependencies 177 • Fifth Normal Form 181 • Domain/Key
Normal Form 181
Chapter 4: Database Design Using Normalization 191

Assess Table Structure 192
Designing Updatable Databases 193
Advantages and Disadvantages of Normalization 193 • Functional Dependencies 194
• Normalizing with SQL 194 • Choosing Not to Use BCNF 196 • Multivalued
Dependencies 196
Designing Read-Only Databases 197
Denormalization 197 • Customized Duplicated Tables 198
Common Design Problems 200
The Multivalue, Multicolumn Problem 200 • Inconsistent Values 202 • Missing
Values 203 • The General-Purpose Remarks Column 204
Chapter 5: Data Modeling with the Entity-Relationship Model 212

The Purpose of a Data Model 213
A01_KROE2749_15_SE_FM.indd 6 14/12/17 4:03 PM

Contents vii
The Entity-Relationship Model 213

Entities 214 • Attributes 214 • Identifiers 214 • Relationships 215 • Maximum
Cardinality 217 • Minimum Cardinality 218 • Entity-Relationship Diagrams and Their
Versions 219 • Variations of the E-R Model 219 • E-R Diagrams Using the IE Crow’s Foot
Model 220 • Strong Entities and Weak Entities 222 • ID-Dependent Entities 222
• Non–ID-Dependent Weak Entities 223 • The Ambiguity of the Weak Entity 224
• Subtype Entities 225
Patterns in Forms, Reports, and E-R Models 227
Strong Entity Relationship Patterns 228 • ID-Dependent Relationship Patterns 231
• Mixed Identifying and Nonidentifying Relationship Patterns 238 • The For-Use-By Subtype
Pattern 241 • Recursive Relationship Patterns 242
The Data Modeling Process 245
The College Report 246 • The Department Report 247 • The Department/Major
Report 249 • The Student Acceptance Letter 249
Chapter 6: Transforming Data Models into Database Designs 267

The Purpose of a Database Design 268
Create a Table for Each Entity 268
Selecting the Primary Key 268 • Specifying Alternate Keys 271 • Specifying Column
Properties 271 • Verify Normalization 278
Create Relationships 279
Relationships Between Strong Entities 279 • Relationships Using ID-Dependent
Entities 283 • Relationships with a Weak Non–ID-Dependent Entity 287 • Relationships in
Mixed Entity Designs 288 • Relationships Between Supertype and Subtype Entities 289
• Recursive Relationships 290 • Representing Ternary and Higher-Order Relationships 292
• Relational Representation of the Highline University Data Model 295
Design for Minimum Cardinality 296
Actions when the Parent Is Required 297 • Actions when the Child Is
Required 299 • Implementing Actions for M-O Relationships 300 • Implementing Actions
for O-M Relationships 301 • Implementing Actions for M-M Relationships 301 • Designing
Special Case M-M Relationships 302 • Documenting the Minimum Cardinality Design 302
• An Additional Complication 304 • Summary of Minimum Cardinality Design 304
The View Ridge Gallery Database 305
View Ridge Gallery Database Summary of Requirements 305 • The View Ridge
Data Model 306 • Database Design with Data Keys 307 • Minimum Cardinality
Enforcement for Required Parents 308 • Minimum Cardinality Enforcement for the Required
Child 310 • Column Properties for the View Ridge Database Design Tables 311
PART 3 ■ Database Implementation 323
Chapter 7: SQL for Database Construction and Application

Processing 324
The Importance of Working with an Installed DBMS Product 325
The View Ridge Gallery Database 325
SQL DDL and DML 325

viii Contents
Managing Table Structure with SQL DDL 327

Creating the VRG Database 327 • Using SQL Scripts 327 • Using the SQL CREATE
TABLE Statement 328 • Variations in SQL Data Types and SQL/PSM 329 • Creating the
VRG Database ARTIST Table 329 • Creating the VRG Database WORK Table and the 1: N
ARTIST-to-WORK Relationship 332 • Implementing Required Parent Rows 333
• Implementing 1:1 Relationships 334 • Casual Relationships 334 • Creating Default
Values and Data Constraints with SQL 335 • Creating the VRG Database Tables 336
• The SQL ALTER TABLE Statement 340 • The SQL DROP TABLE Statement 340
• The SQL TRUNCATE TABLE Statement 341 • The SQL CREATE INDEX
Statement 341
SQL DML Statements 342
The SQL INSERT Statement 342 • Populating the VRG Database Tables 343 • The
SQL UPDATE Statement 349 • The SQL MERGE Statement 350 • The SQL DELETE
Statement 351
Using SQL Views 352
Using SQL Views to Hide Columns and Rows 355 • Using SQL Views to Display Results of
Computed Columns 356 • Using SQL Views to Hide Complicated SQL Syntax 357
• Layering Built-in Functions 358 • Using SQL Views for Isolation, Multiple Permissions, and
Multiple Triggers 360 • Updating SQL Views 361
Embedding SQL in Program Code 362
SQL/Persistent Stored Modules (SQL/PSM) 364 • Using SQL User-Defined
Functions 364 • Using SQL Triggers 367 • Using Stored Procedures 373 • Comparing
User-Defined Functions, Triggers, and Stored Procedures 376
Chapter 8: Database Redesign 424

The Need for Database Redesign 425
SQL Statements for Checking Functional Dependencies 425
What Is a Correlated Subquery? 426
How Do I Analyze an Existing Database? 431
Reverse Engineering 432 • Dependency Graphs 433 • Database Backup and Test
Databases 433
Changing Table Names and Table Columns 434
Changing Table Names 434 • Adding and Dropping Columns 436 • Changing a Column
Data Type or Column Constraints 437 • Adding and Dropping Constraints 438
Changing Relationship Cardinalities 438
Changing Minimum Cardinalities 438 • Changing Maximum Cardinalities 439
Adding and Deleting Tables and Relationships 442
Forward Engineering 443
PART 4 ■ Multiuser Database Processing 453
Chapter 9: Managing Multiuser Databases 454

The Importance of Working with an Installed DBMS Product 455
Database Administration 455
Managing the Database Structure 456

Contents ix
Concurrency Control 457

The Need for Atomic Transactions 458 • Resource Locking 461 • Optimistic Versus
Pessimistic Locking 463 • SQL Transaction Control Language and Declaring Lock
Characteristics 464 • Implicit and Explicit COMMIT TRANSACTION 466 • Consistent
Transactions 466 • Transaction Isolation Level 467 • SQL Cursors 468
Database Security 470
Processing Rights and Responsibilities 470 • DBMS Security 471 • DBMS Security
Guidelines 472 • Application Security 474 • The SQL Injection Attack 475
Database Backup and Recovery 475
Recovery via Reprocessing 476 • Recovery via Rollback/Rollforward 476
Managing the DBMS 479
Maintaining the Data Repository 480
Chapter 10: Managing Databases with Microsoft SQL Server 2017,

Oracle Database, and MySQL 5.7 490
Installing the DBMS 491
Using the DBMS Database Administration and Database Development Utilities 492
Creating a Database 492
Creating and Running SQL Scripts 492
Reviewing the Database Structure in the DBMS GUI Utility 493
Creating and Populating the View Ridge Gallery VRG Database Tables 493
Creating SQL Views for the View Ridge Gallery VRG Database 493
Importing Microsoft Excel Data into a Database Table 493
Database Application Logic and SQL/Persistent Stored Modules (SQL/PSM) 493
DBMS Concurrency Control 494
DBMS Security 494
DBMS Database Backup and Recovery 494
Other DBMS Topics Not Discussed 494
Choose Your DBMS Product(s)! 495
Summary 495 • Key Terms 496 • Exercises 496
ONLINE CHAPTER: SEE PAGE 495 FOR INSTRUCTIONS

Chapter 10A: Managing Databases with Microsoft SQL
Server 2017
Chapter Objectives
The Microsoft SQL Server 2017 DBMS
Installing Microsoft SQL Server 2017
Installing Microsoft SQL Server 2017 Required Software • Installing the Microsoft
SQL Server 2017 DBMS • Installing Microsoft SQL Server 2017 Reporting
Services
Microsoft SQL Server 2017 Utilities
SQL CMD and Microsoft PowerShell • Microsoft SQL CLR • The Microsoft SQL Server
Management Studio
Using Microsoft SQL Server 2017
Creating a Microsoft SQL Server 2017 Database
Microsoft SQL Server 2017 SQL Statements and SQL Scripts
Using Existing SQL Scripts • Using a Single SQL Script to Store Multiple SQL Commands
Implementing the View Ridge Gallery VRG Database in Microsoft SQL Server 2017

x Contents
Using SQL Scripts to Create and Populate Database Tables • Creating the View Ridge
Gallery VRG Database Table Structure • Reviewing Database Structures in the SQL
Server GUI Display • Indexes • Populating the VRG Database Tables with Data
• Creating SQL Views
Importing Microsoft Excel Data into a Microsoft SQL Server Database Table
Microsoft SQL Server 2017 Application Logic
Transact-SQL • User-Defined Functions • Stored Procedures • Triggers
Microsoft SQL Server 2017 Concurrency Control
Transaction Isolation Level • Cursor Concurrency • Locking Hints
Microsoft SQL Server 2017 Security
SQL Server 2017 Database Security Settings
Microsoft SQL Server 2017 Backup and Recovery
Backing Up a Database • SQL Server Recovery Models • Restoring a Database
• Database Maintenance Plans
Topics Not Discussed in This Chapter
Summary • Key Terms • Review Questions • Exercises • Case Questions
• The Queen Anne Curiosity Shop Project Questions • Morgan Importing Project
Questions

Chapter 10B: Managing Databases with Oracle Database
Chapter Objectives
The Oracle Corporation Oracle Database DBMS
Installing Oracle Database
Installing a Loopback Adapter • Oracle Database, Java, JavaScript, and the Adobe
Flash Player • Oracle Database 12c Release 2 Documentation • Downloading Oracle
Database • Installing Oracle Database 12c Release 2 with the Oracle Universal
Installer (OUI) • Installing Oracle Database Express Edition 11g Release 2 (Oracle
Database XE)
Oracle Database Administration and Development Tools
The Oracle Database 12c Release 2 Configuration Assistant • The Oracle Enterprise Manager
Database Express 12c Database Administration Utility • The Oracle Database XE 11.2
Database Administration Utility
Oracle Database Tablespaces
Oracle Database Security
User Privileges • Creating a User Account • Creating a Role
Oracle Database Application Development Tools
Oracle SQL*Plus • Oracle SQL Developer • Creating a Workspace for the SQL Developer
Files • Oracle Database Schemas
Creating and Using an Oracle Database Database
Creating a Database in Oracle Database • Oracle Database SQL Statements and SQL
Scripts • Using Existing SQL Scripts • Using a Single SQL Script to Store Multiple SQL
Commands
Implementing the View Ridge Gallery VRG Database in Oracle Database
Using SQL Scripts to Create and Populate Database Tables • Creating the View Ridge
Gallery VRG Database Table Structure • Transaction COMMIT in Oracle Database
• Reviewing Database Structures in the SQL Developer GUI Display • Indexes
• Populating the VRG Tables • Creating SQL Views
Importing Microsoft Excel Data into an Oracle Database Table
Oracle Database Application Logic
Oracle Database PL/SQL • User-Defined Functions • Stored Procedures
• Triggers

Contents xi
Oracle Database Concurrency Control

Read-Committed Transaction Isolation Level • Serializable Transaction Isolation Level
• Read-Only Transaction Isolation • Additional Locking Comments
Oracle Database Backup and Recovery
Oracle Database Recovery Facilities • Types of Failure
• The Queen Anne Curiosity Shop Project Questions • Morgan Importing
Project Questions

Chapter 10C: Managing Databases with MySQL 5.7
Chapter Objectives
The MySQL 5.7 DBMS
Installing MySQL Community Server 5.7
The MySQL Installer • MySQL Storage Engines
The MySQL Utilities
The MySQL Command-Line Client • The MySQL Workbench GUI Utility • Creating a
Workspace for the MySQL Workbench Files
Creating and Using a MySQL Database
Creating a Database in MySQL • Setting the Active Database in MySQL • MySQL SQL
Statements and SQL Scripts • Using Existing SQL Scripts • Using a Single SQL Script to
Store Multiple SQL Commands
Implementing the View Ridge Gallery VRG Database in MySQL 5.7
Creating the VRG Database • Using SQL Scripts to Create and Populate Database Tables
• Creating the View Ridge Database Table Structure • Reviewing Database Structures in the
MySQL GUI Display • Indexes • Populating the VRG Tables with Data • Transaction
COMMIT in MySQL • Creating SQL Views
Importing Microsoft Excel Data into a MySQL 5.7 Database Table
MySQL Application Logic
MySQL SQL/PSM Procedural Statements • User-Defined Functions • Stored
Procedures • Triggers • A Last Word on MySQL Stored Procedures and Triggers
Concurrency Control
MySQL 5.7 Security
Creating a New User • MySQL Database Security Settings
MySQL 5.7 DBMS Backup and Recovery
Backing Up a MySQL Database • Restoring a MySQL Database
Project Questions
PART 5 ■ Database Access Standards 497
Chapter 11: The Web Server Environment 498

A Web Database Application for the View Ridge Gallery 500
The Web Database Processing Environment 501
Database Server Access Standards 502
The ODBC Standard 503
ODBC Architecture 504 • Conformance Levels 505 • Creating an ODBC Data Source
Name 506

xii Contents
The Microsoft .NET Framework and ADO.NET 512

OLE DB 514 • ADO and ADO.NET 518 • The ADO.NET Object Model 518
The Java Platform 523
JDBC 523 • Java Server Pages (JSP) and Servlets 525 • Apache Tomcat 525
Web Database Processing with PHP 527
Web Database Processing with PHP and the NetBeans IDE 527 • Getting Started with
HTML Web Pages 530 • The index.html Web Page 530 • Creating the index.html Web
Page 530 • Using PHP 533
Web Page Examples with PHP 540
Example 1: Updating a Table 541 • Example 2: Using PHP Data Objects (PDO) 545
• Example 3: Invoking a Stored Procedure 546 • Challenges for Web Database
Processing 553 • SQL Injection Attacks 554
Extensible Markup Language (XML) 555
The Importance of XML 555 • XML as a Markup Language 556
Creating XML Documents from Database Data 557
Using the SQL SELECT … FOR XML Statement 557
Chapter 12: Data Warehouses, Business Intelligence Systems,

and Big Data 569
Business Intelligence Systems 571
The Relationship Between Operational and BI Systems 571
Reporting Systems and Data Mining Applications 571
Reporting Systems 572 • Data Mining Applications 573
Data Warehouses and Data Marts 573
Components of a Data Warehouse 573 • Data Warehouses Versus Data Marts 577
• Dimensional Databases 578
Reporting Systems 586
RFM Analysis 586 • OLAP 588
Data Mining 597
Distributed Database Processing 599
Types of Distributed Databases 599 • Challenges of Distributed Databases 600
Object-Relational Databases 601
Virtualization 602
Cloud Computing 603
Big Data and the Not Only SQL Movement 607
Column Family Databases 608 • MapReduce 610 • Hadoop 610
• Case Questions 617 • The Queen Anne Curiosity Shop Project
Questions 618 • Morgan Importing Project Questions 619
Appendices
ONLINE APPENDICES: SEE PAGE 620 FOR INSTRUCTIONS

Appendix A: Getting Started with Microsoft Access 2016
Chapter Objectives
What Is the Purpose of This Appendix?
Why Should I Learn to Use Microsoft Access 2016?
What Will This Appendix Teach Me?
What Is a Table Key?
What are Relationships?

Contents xiii
How Do I Create a New Microsoft Access 2016 Database?

What is the Microsoft Office Fluent User Interface?
The Ribbon and Command Tabs • Contextual Command Tabs • Modifying the Quick Access
Toolbar • Database Objects and the Navigation Pane
How Do I Close a Database and Exit Microsoft Access 2016?
How Do I Open an Existing Microsoft Access 2016 Database?
How Do I Create Microsoft Access 2016 Database Tables?
How Do I Insert Data into Tables Using the Datasheet View?
Modifying and Deleting Data in Tables in the Datasheet View
How Do I Create Relationships Between Tables?
How Do I Create and Run Microsoft Access 2016 Queries?
How Do I Create Microsoft Access 2016 Forms and Reports?
How Do I Close a Newly-Created Database and Exit Microsoft Access 2016?
Key Terms • Review Questions • Exercises
Appendix B: Getting Started with Systems Analysis and Design

Chapter Objectives
What Is Information?
What Is an Information System?
What Is a Competitive Strategy?
How Does a Company Organize Itself Based on Its Competitive Strategy?
What Is a Business Process?
How Do Information Systems Support Business Processes?
Do Information Systems Include Processes?
Do We Have to Understand Business Processes in Order to Create Information Systems?
What Is Systems Analysis and Design?
What Are the Steps in the SDLC?
The System Definition Step • The Requirements Analysis Step • The Component Design Step
• The Implementation Step • The System Maintenance Step
What SDLC Details Do We Need to Know?
What Is Business Process Modeling Notation?
What Is Project Scope?
How Do I Gather Data and Information About System Requirements?
How Do Use Cases Provide Data and Information About System Requirements?
The Highline University Database
The College Report • The Department Report • The Department/Major Report
• The Student Acceptance Letter
What Are Business Rules?
What Is a User Requirements Document (URD)?
What Is a Statement of Work (SOW)?
Appendix C: E-R Diagrams and the IDEF1X and UML Standards

Chapter Objectives
Why Should I Learn to Use IDEF1X or UML?
What are IDEF1X Entities?
What are IDEF1X Relationships?
Nonidentifying Connection Relationships • Identifying Connection Relationships • Nonspecific
Relationships • Categorization Relationships
What are Domains?
Domains Reduce Ambiguity • Domains Are Useful • Base Domains and Typed Domains

xiv Contents
How Does UML Represent Entities and Relationships?

Representation of Strong Entities • Representation of Weak Entities • Representation of Subtypes
What OOP Constructs Are Introduced by UML?
What is the Role of UML in Database Processing Today?
Key Terms • Review Questions
Appendix D: Getting Started with Microsoft Visio 2016

Chapter Objectives
Why Should I Learn to Use Microsoft Visio 2016?
What Won’t This Appendix Teach Me?
How Do I Start Microsoft Visio 2016?
How Do I Create a Database Model Diagram in Microsoft Visio 2016?
How Do I Name and Save a Database Model Diagram in Microsoft Visio 2016?
How Do I Create Entities in a Database Model Diagram in Microsoft Visio 2016?
How Do I Create Relationships Between Entities in a Database Model Diagram in
Microsoft Visio 2016?
How Do I Create Data Models in Microsoft Visio 2016?
How Do I Create Database Designs in Microsoft Visio 2016?
Appendix E: Getting Started with the MySQL Workbench

Data Modeling Tools
Chapter Objectives
Why Should I Learn to Use the MySQL Workbench Data Modeling Tools?
What Won’t This Appendix Teach Me?
How Do I Start the MySQL Workbench?
How Do I Create a Workspace for the MySQL Workbench Files?
How Do I Create Database Designs in the MySQL Workbench?
How Do I Create a Database Model and E-R Diagram in the MySQL Workbench?
Appendix F: The Semantic Object Model

Chapter Objectives
Why Should I Learn to Use the Semantic Object Model?
What Are Semantic Objects?
What Semantic Objects Are Used in the Semantic Object Model?
What Are Semantic Object Attributes? • Attribute Cardinality • What Are Object
Identifiers? • What Are Attribute Domains? • What Are Semantic Object Views?
What Types of Objects Are Used in the Semantic Object Model?
What Are Simple Objects? • What Are Composite Objects? • What Are Compound Objects?
• How Do We Represent One-to-One Compound Objects as Relational Structures? • How Do
We Represent One-to-Many and Many-to-One Relationships as Relational Structures? • How
Do We Represent Many-to-Many Relationship Objects as Relational Structures? • What Are
Hybrid Objects? • How Do We Represent Hybrid Relationships in Relational Structures?
• What Are Association Objects? • What Are Parent/Subtype Objects? • What Are
Archetype/Version Objects?
Comparing the Semantic Object and the E-R Models

Contents xv
Appendix G: Physical Database Design and Data Structures for

Database Processing
Chapter Objectives
Introduction to Physical Database Design
What Are Flat Files?
Processing Flat Files in Multiple Orders • A Note on Record Addressing • How Can Linked Lists
Be Used to Maintain Logical Record Order? • How Can Indexes Be Used to Maintain Logical
Record Order? • B-Trees • Summary of Data Structures
How Can We Represent Binary Relationships?
A Review of Record Relationships • How Can We Represent Trees? • How Can We Represent
Simple Networks? • How Can We Represent Complex Networks? • Summary of Relationship
Representations
How Can We Represent Secondary Keys?
How Can We Represent Secondary Keys with Linked Lists? • How Can We Represent Secondary
Keys with Indexes?
Multicolumn Indexes
Clustering
Decomposition
Vertical Decomposition • Horizontal Decomposition
Appendix H: Getting Started with Web Servers, PHP, and the NetBeans IDE
Chapter Objectives
Which Operating System are we Discussing?
How Do I Install a Web Server?
How Do I Set Up IIS in Windows 10?
How Do I Manage IIS in Windows 10?
How Is a Web Site Structured?
How Do I View a Web Page from the IIS Web Server?
How Is Web Site Security Managed?
What is Java?
What Is the NetBeans IDE?
How Do I Install the Java Development Kit (JDK) and the NetBeans IDE?
What Is PHP?
How Do I Install PHP?
How Do I Check PHP to Make Sure it is Running Correctly?
How Do I Create a Web Page Using the NetBeans IDE?
How Do I Manage the PHP Configuration?
Appendix I: XML
Chapter Objectives
Extensible Markup Language (XML)
XML as a Markup Language • Materializing XML Documents with XSLT
XML Schema versus Document Type Declarations
XML Schema Validation • Elements and Attributes • Flat Versus Structured Schemas
• Global Elements
Creating XML Documents from Database Data
Using the SQL SELECT . . . FOR XML Statement • Multi-table SELECT with FOR XML
• An XML Schema for All CUSTOMER Purchases • A Schema with Two Multivalued Paths

xvi Contents
Why Is XML Important?

Additional XML Standards
Summary • Key Terms • Review Questions • Exercises
Appendix J: Business Intelligence Systems

Chapter Objectives
Business Intelligence Systems
Reporting Systems and Data Mining Applications
Reporting Systems • Data Mining Applications
The Components of a Data Warehouse
Data Warehouses and Data Marts • Data Warehouses and Dimensional Databases
Reporting Systems
OLAP • RFM Analysis • Reporting System Components • Reporting System Functions
Data Mining
Unsupervised versus Supervised Data Mining • Four Popular Data Mining Techniques
• Market Basket Analysis • Decision Trees
Project Questions
Appendix K: Big Data

Chapter Objectives
What Is Big Data?
The Three Vs and the “Wanna Vs” • Big Data and NoSQL Systems • The CAP Theorem
Non-Relational Database Management Systems
Key-Value Databases • Document Databases • Column Family Databases • Graph Databases
Using a Cloud Database Management System
Migrating an Existing Local Database to Microsoft Azure Cosmos DB • Using SQL to Create a
New Database on Microsoft Azure Cosmos DB
Big Data, NoSQL Systems, and the Future
Appendix L: JSON and Document Databases

Chapter Objectives
Document Database Basics
JSON Data Structuring
Introducing ArangoDB
Downloading and Installing ArangoDB
Creating Data in ArangoDB
Simple Document Examples • Complex Document Examples • Logical Design Choices
Querying Data in ArangoDB
Using HTTP • Using a Programming Language • Using ArangoDB Query Language (AQL)
Physical Design Choices in ArangoDB
Indexing • Data Distribution
Document Databases in the Cloud
Creating a Document Database in Microsoft Azure Cosmos DB • Querying a Document
Database in Microsoft Azure Cosmos DB
Bibliography 621
Glossary 623
Index 639

Foreword to the 40th Anniversary Edition
David Kroenke
The publisher has asked me to write a short history of this text for this, the 40th anniversary
edition. The details of each edition and how they changed are instructive, but this text and
the discipline of database processing grew up together, and the story of how that happened
might be more helpful to students who will work in disciplines, such as Big Data, that are
emerging today.
We Didn’t Know What We Were Doing

Database processing technology originated in the period 1970 to 1975, though not necessar-
ily by that name. At the time, the U.S. government used the term data bank. Others used data
base as well as database. I liked the latter and used it when I began work on this text in 1975.
In 1971, I was an officer in the U.S. Air Force, assigned to a Pentagon team that was
building and using a simulation of World War III. It was the height of the Cold War, and
the Department of Defense wanted a means to assess the efficacy of current and proposed
weapons systems.
By a stroke of good luck, I was assigned to work on the data manager portion of that
simulation (the term Database Management System [DBMS] was not yet in use). The logical data
model of that data manager was similar to that of the set-based system that Bachmann had
developed at General Electric (then a mainframe manufacturer) and that later became the
CODASYL DBTG standard.1
Our simulation was slow and long-running; a typical run would take 10 to 12 hours. We
were constrained more by input and output of data than by CPU time, and I developed low-
level, re-entrant, assembly language routines for getting and putting data to and from main
memory on parallel channels.
In addition to our project and Bachmann’s, IBM was developing a manufacturing-
oriented data manager in concert with North American Aviation. That project eventually
became IBM’s product IMS.2 Another government project of that era resulted in the data
manager named Total.
In retrospect, I’d say the one thing we had in common was that none of us knew what we
were doing. We didn’t have any data models, best practices, or design principles. We didn’t
even know how to program. This was long before GoTo–less programming, which led to
structured programming, and eventually to object-oriented programming. We did know that
life was easier if we developed some sort of a logic chart before we began, but that was about
it. We’d pick up our coding pads (everything was done via punched cards) and start to work.
There were no debugging tools. When a job would fail, we’d receive a hexadecimal
printout of the CPU registers and the contents of main memory (the printout would be 12 to
18 inches thick). There were no hexadecimal calculators, so we’d manually add and subtract
1
CODASYL, the Committee on Data Systems Languages, was the committee, chaired by Grace Hopper (see
https://en.wikipedia.org/wiki/Grace_Hopper), that developed the COBOL language standard. DBTG, the database
task group, was a subcommittee tasked with developing a data modeling standard. The DBTG model was
popular for a short while, but was replaced by the relational model by the 1980s.
2
IBM IMS is still a functional DBMS product—see www-01.ibm.com/software/data/ims/index.html.
xvii

xviii Foreword to the 40th Anniversary Edition
hexadecimal numbers to navigate our way around the printout, sticking rulers in the listing as
place markers. Stiff, wooden rulers were the best.
Again, though, we were just trying to solve a problem. We didn’t have any idea that the
technology we were developing would become an important part of the emerging world.
Imagine Amazon or your college without database processing. But all of that was in the future.
We were just trying to get the “darn thing” to run and somehow solve the particular problem
that we’d been assigned.
For example, an important function of those early systems was to manage relationships.
In our simulation, we had bombers and tankers and opposing radar sites and opposing air-to-
air missiles. We needed to keep track of which of those was assigned or related to which. We
just wrote programs to do that. A decade or two later someone discovered in surprise, “Hey,
there’s as much information in the relationships as there is in the data.”
We made stuff up as we went along. The first edition of this text included no definition
of database. When a reviewer pointed that out, I made one up for the second edition. “A self-
describing collection of integrated records.” Completely fabricated, but it’s worked now for
35 years, so it must have been serviceable.
Situations like that were common in those early projects. We made stuff up that would
help us solve our problem. Progress was slow, mistakes were frequent, failures were common.
Millions of dollars and labor hours were wasted. But gradually, over time, database technol-
ogy emerged.
Origin of This Text
In 1973 I completed my military commitment and following John Denver’s song “Rocky
Mountain High” moved my family from Washington, D.C., to Colorado State University. The
business school hired me as an instructor while I attended graduate school in statistics and
engineering across the street. To my delight, I was assigned to teach a course entitled File
Management, the predecessor of today’s Database Processing course (see Figure FM-1).
As with any young instructor, I wanted to teach what I knew and that was the rudiments
of database processing. So, I began to formulate a database course and by the spring of 1975,
was looking for a textbook. I asked the book reps if they had such a book and none did. The
sales rep for SRA, however, asked, “No, but we’re looking for one. Why don’t you write it?” My
department chair, Bob Rademacher, encouraged me to do so, and on June 29, 1975, I signed
the contract.
FIGURE FM-1
David Kroenke Loses
Control of Students Excited
by Database Technology

Foreword to the 40th Anniversary Edition xix
FIGURE FM-2
How Textbooks Were Written
The draft and all the diagrams were written in number 2 pencil on the back of old coding
sheets, as shown in Figure FM-02. The text would go to a typist, who’d do the best she could
to decipher my writing. I’d proof the typing and she’d produce another typed manuscript
(long before word processing—pages had to be retyped to remove errors). Those pages would
then go to a copy editor and I would redo them again, back to the typist for a round or two.
Eventually, the final typed manuscript would go to a compositor who would produce long gray
sheets (called galleys) of text to be proofed. After that, the text would be glued (I’m not kid-
ding) to make up pages, integrating the art which had been following a similar pathway, and
then those pages would be photographed and sent to a printer.
The final draft of the first edition was completed in January 1976, and the text was pub-
lished in January 1977. We were proud that it only took a year.
Contents of the First Edition
Database Processing was the first such textbook aimed at the information systems market.
C. J. Date had produced Database Systems prior to this text, but his book was aimed at com-
puter science students.3 No one knew what should be in an information systems database
book. I made it up, we sent drafts to reviewers, and they approved it. (They didn’t know
either.)
3
C. J. Date’s book An Introduction to Database Systems is currently in its eighth edition.

xx Foreword to the 40th Anniversary Edition
FIGURE FM-3
Cover of the First Edition
of Database Processing
The first edition (see Figure FM-3) had chapters on file management and data structures.
It also had chapters on hierarchical, network, and relational data models. By the way, E. F.
Codd, the creator of the relational data model, was relatively unknown at that point and he
was happy to review the relational chapter. The text also featured a description of the features
and functions of five DBMS products: ADABAS, System 2000, Total, IDMS, and IMS. (To my
knowledge, only IMS is still in use today.) It wrapped up with a chapter on database adminis-
tration.
When writing that last chapter, I thought it would be a good idea to talk with an auditor
to learn what auditors looked for when auditing database systems. Accordingly, I drove to
Denver and met with one of the top auditors at one of the then-Big-Eight firms. I didn’t learn
much, just some high-level hyperbole about using commonly accepted auditing standards.
The next day, the phone rang in my office and an executive in New York City invited me out to
that firm for a job interview for a position to develop and teach database auditing standards to
their staff. None of us knew what we were doing!
I had no idea of how incredibly fortunate I was. To stumble into a discipline that would
become one of the most important in the information systems field, to have experience and
knowledge to put into a text, to have a supportive department, and, finally, to have what was at
that time a superb publisher with an outstanding sales and marketing team (see Figure FM-4).
Because it was all I had known, I thought it was normal. Ah, youth.
Lessons Learned
At age 71, I’m not quite consigned to watching the daytime weather channel but have
reached the stage when people start listing lessons learned. I’ll try to keep it brief. Here are
my five lessons learned, developed both as a database technology bystander and participant:

Foreword to the 40th Anniversary Edition xxi
FIGURE FM-4
Hot Marketing Handout
1977—Note Text Price
Don’t Confuse Luck with Exceptional Ability

According to an independent study at the time, the second edition of this text had 91 percent
of the market. It was the first, and it had a great publisher with a superb sales force. That suc-
cess was due, truly, to lucky timing and good fortune. At that point I should have doubled
down and made sure that the 91 percent were satisfied while sending Thanksgiving turkeys to
the 9 percent not in the fold.
Instead, what did I do? Ignored the book and joined Microrim to help develop the R:Base
products.4 Five years later when I returned to the book, numerous competitors had emerged
and the book lost half of its market. I’d thought I could jump back in and regain that early suc-
cess, but the market had a hard lesson for me.
I mention this because I’ve seen it elsewhere as well. Microsoft was built and managed
by superior business professionals like Bill Gates, Steve Ballmer, Jon Shirley, Steve Okey, and,
in the database domain, David Kaplan. Between 1985 and 2000, hundreds of employees
joined the firm and were issued stock options. They were largely competent professionals,
but no different from the same level of professionals one would have found at 3M, Procter
and Gamble, Boeing, etc. The difference was that during that interval, their Microsoft stock
split seven times.
Many of those competent professionals understood that they had been very, very lucky
to get on the Microsoft bus when they did. They took their stock proceeds and re-invested in
index funds or something else safe and have been enjoying life on the golf course with their
4
For more information on R:Base, see the Wikipedia article R:Base (https://en.wikipedia.org/wiki/R:Base). Now
called RBASE, this is still a functional DBMS product—see http://www.rbase.com/.

xxii Foreword to the 40th Anniversary Edition
families ever since. However, some of the just-competent professionals confused their good
luck with exceptional personal ability and founded their own companies or started venture
capital firms. Most lost their money. They were good, but they weren’t of the same caliber as
Gates et al.
Joseph Conrad said it, “It is the mark of an inexperienced man not to believe in luck.”
Marketing Trumps Technology

If you have a chance to invest in an average technology with superb marketing or superb
technology with average marketing, take the former. Marketing is far more important than
technology.
IBM’s IMS uses a hierarchical data model. Representing many-to-many relationships
with hierarchies is a pain. With IMS the database developer is forced to write all sorts of
design and coding machinations that should have been done by the DBMS or avoided by
using a different DBMS. In the early days, I watched an IBM technical sales representative
present those machinations as a skill that every good database developer must already have.
“Surely you know how to do the XYZ?” (I don’t remember the name they’d given that dance).
Because none of us in the audience knew any better, we all assumed that we were deficient
if we didn’t know how to do the XYZ. The deficiency was in the product, not us, but we were
duped by good marketing.
Developed by Wayne Ratcliff, Ashton-Tate’s dBase5 was the most successful relational
microcomputer DBMS product until Microsoft entered the picture with Microsoft Access.
In fact, dBase was neither a DBMS nor was it relational—it was a file management system.
However, Ashton-Tate’s marketing convinced Osborne to place a free copy of dBase on every
one of its Osborne II computers. The Osborne II was the micro or personal computer (PC)
of choice for a new cadre of application developers, and they wrote millions of lines of dBase
code. They used what they had and thought it was fine. When better products came along,
there was no way that any small developer was going to rewrite existing code or learn new
products. The new graphical user interface in Microsoft Windows, the Microsoft Office pack-
age, and cheap Microsoft Access pricing was the only force strong enough to push Ashton-Tate
off its leading position.
Salsa, a product that I helped Wall Data develop, implemented the semantic object
model (which we discuss in Appendix F), and was selected as the runner-up to Netscape
Navigator for product of the year in 1996 (the other runner-up was Internet Explorer). Salsa
failed—not because of the technology, but because of the marketing. We tried to sell it as an
end-user product and it was a developer product. It was as if we’d invented Gore-Tex and we
were out trying to sell it to people standing in the rain. We should have sold it to the clothing
manufacturers. Marketing 101. I still have nightmares about the superior technology that
washed down that drain.
Christensen’s Model Informs

I don’t know anyone who made substantial money in mainframes that did well in the
microcomputer industry. Accustomed to the features and power of mainframes, we
viewed microcomputers as toys. We termed the TRS-80 micro the Trash-80. I bought
an early Apple and it crashed on me and I thought to myself, “This will never amount
to anything.”
This phenomenon is addressed by Clayton Christensen is his disruptive innovation
model.6 His thesis is that when a disruptive technology comes along, companies that have
success in the disrupted technology are unable to capitalize on the opportunities of the new
technology. Kodak could not adapt to digital photography; Swiss watch makers could not
adapt to digital watches. Textbook publishers could not adapt to book rentals and used books
sales by Amazon. Microsoft lost its way when it achieved its goal of “A computer on every desk
and in every home.” It struggled to adapt to the Internet.
5
dBbase is still a functional DBMS product—see http://www.dbase.com
6
Christensen, Clayton M. The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail (Reprint edi-
tion). (Brighton, MA: Harvard Business Review Press, 2106)

Foreword to the 40th Anniversary Edition xxiii
Don’t look for the market leaders in big data or robotics to come from existing, large ven-
dors. They will come from smaller companies that can position themselves to thrive in the
new environment. If you haven’t learned Christensen’s model, you should.
Good-enough Fashion Will Do

For the most part, the relational model supplanted all the other data models. Because of Codd’s
insights on the use of functional dependencies for relational design, it provided sound design
principles. Also, fixed-length records (as, in practice, they were at first) fit nicely with existing
file management capabilities. It worked. Thousands of papers were written on the topic.
However, today’s technology readily supports the storage and searching of multiple fields
in un-normalized documents. In 1980, technology constraints required designers to take a
document like a sales order and break it up into its pieces: Invoice, Salesperson, Customer,
Line-item, Product. They would then store those pieces and then put them all back together
with SQL (Structured Query Language) when someone wanted the original sales order. That
makes no sense today. It’s like driving your car into a parking garage and having staff pull off
your front tires and put them in the pile of front tires, your steering wheel into a pile of steer-
ing wheels, etc. Then, when you come back, put it all back together. Even though it’s unneces-
sary, it’s happening right now in zillions of data centers.
So why is the relational model still in use? Because it’s good enough and still in fashion.
Fashion is important. Consider normalization theory. Codd’s first paper addressed nor-
malization through third normal form. However, in later papers, he and others showed that
this wasn’t enough. Relations in third normal form still had anomalies, which led to fourth
and fifth and then Boyce-Codd (BCNF) Normal Forms. Despite this, one still hears people
talk about third normal form as the be-all, end-all of relational design. Third normal form is
good enough and still in fashion. It was as if progress stopped at third normal form (not in this
text, though, where all of these forms are taught).
I suspect that someday soon, the whole relational mess will no longer be good enough
and we’ll move to XML or JSON or some other form of document storage (as we discuss in
Chapter 12, Appendix I, and Appendix L). I’ve been saying that for 10 years, though, and it
hasn’t happened yet.
Another example of good enough and fashion is the entity-relationship (ER) model.
The ER model is nothing more than a thin cover over the relational model. Entities
are essentially logical relations, and relationships are a slim version of foreign keys. ER
operates at too low a level of abstraction. Other models like the semantic object model
and other object-oriented models are better. None succeeded. The ER model was in
fashion and good enough.
When It’s Over, It’s Over

By the turn of the century, I’d been writing and revising this text for 25 years. Although I was
exceedingly grateful to the thousands of professors and students who had used this book over
those years, I also knew I was done. Partly, I said to myself, because it had settled down, the early
crazy days were long gone, and partly because 25 years is a long time to work on a textbook.
To my great good fortune, I found David Auer, who agreed to take over the revisions of
this text. I am most grateful to David for his hard work and for his fidelity to the underlying
goals and philosophy of this text. The rest of this story is his.
David Auer
I was introduced to David Kroenke while working on the Instructor’s Manual for the
ninth edition of Database Processing. Because we were both living and teaching in western
Washington State, we could get together for meals and discussions. This led to my working
on the companion textbook, Database Concepts, being a technical reader for the 10th edition
of Database Processing, and then being asked to become a coauthor for the 11th edition of
Database Processing.

Another random document with
no related content on Scribd:
He and Miles dined—then Pembroke, over the wine, opened the
Colonel’s billet. It was brief.
“My Dear Boy,—Olivia and I are coming to
Washington to spend the winter. I have not been to the
cursed town since the winter before the war, when
Wigfall was in the Senate, and Floyd was Secretary of
War. John B. Floyd was one of the greatest men the
State of Virginia ever produced. Now, I want to go to a
decent tavern—but Olivia, who is a girl of spirit, won’t
do it. She insists on having a furnished house, and I’ve
engaged one through an agent. Don’t suppose it will
suit, but Olivia swears it will. We’ll be up in the course
of a week or two, and will let you know. Damme if I
expect to find a gentleman in public life—always
excepting yourself, my dear boy. I inclose you our
address. Olivia desires her regards to you and her
particular love to Miles, also mine.
“Sincerely, your friend,
“Th. Berkeley.”
“That’s pleasant news,” said Miles.
“Very pleasant,” replied Pembroke, without smiling in the least.
He was glad to see the Colonel, but he was still sore about Olivia.
Whenever he had been at home, the same friendly intercourse had
gone on as before—but there was always an invisible restraint
between them. Colonel Berkeley had noticed it, and at last ventured
to question Olivia about it—when that young woman had turned on
her father and cowed him by a look of her eye. There were some
liberties the Colonel could not take with his daughter.
Promptly, the Colonel and Olivia arrived.
The house, which was after the conventional pattern of the
Washington furnished house of those days, struck a chill to Colonel
Berkeley’s heart.
“My love,” he said, disconsolately, looking at the dull grates in the
two square drawing-rooms, “I’m afraid I’ll lose all my domestic virtues
around this miserable travesty of a hearth.”
“Just wait, papa,” answered Olivia, with one of her encouraging
smiles.
“I knew how it would be. Wait until some of those big boxes are
unpacked that you swore so about.”
When the boxes were unpacked, they were found to contain the
old fashioned brass andirons and fenders that had shone upon the
cheerful hearths at Isleham for many years. Olivia in a trice, had the
grates out and managed to have a wood fire sparkling where once
they were. Then she produced a great porcelain lamp they had
brought from France with them, and some tall silver candlesticks and
candelabra, which vastly improved the mantels, and she re-arranged
the tasteless furniture and bric-à-brac with such skill that she
cheated herself as well as others into believing them pretty.
It was rather an effort to Pembroke, his first visit. He would not
take Miles with him lest he should seem to fear to go alone. It was
now five years past. Naturally they had met often, but in some way,
this meeting impressed him differently. He had at last waked up to
the fact that he could not forget Olivia Berkeley. It angered him
against himself—and so it was in rather an unamiable mood that he
left the House early, and took his way through a drizzling rain to the
Berkeleys’. When he rung the bell, Petrarch’s familiar black face
greeted him.
“Hi, howdy, Marse French. It do my heart good ter see you. Ole
Marse, I spec he everlastin’ cuss when he fin’ out you been here an’
he ain’t home. Miss Livy, she in de settin’ room.”
“And how are you all getting on here?” asked Pembroke, as
Petrarch officiously helped him off with his great-coat.
“Tollerbul, tollerbul, sir. Old marse, he mighty orkard sometimes.
He swar an’ takes de Lord’s name in vain, spite o’ de commandment
‘Doan never you swar at all.’ I try ter make him behave hisse’f ter de
policemens an’ sech, but he quile all de time he gwine long de
street.”
He ushered Pembroke through the drawing-room, into a little
room beyond. On a sofa drawn up to the wood fire, sat Olivia,
making a pretty home-like picture, in the half light, contrasted with
the dreary drawing-room beyond, and the dismal drizzle outside.
They had not met for nearly two years. The session of Congress
had lasted almost through the year, and when he had been in the
county last, Olivia was away in the mountains. He noticed instantly
that she was very, very pretty, but her beauty had taken a graver and
more womanly cast. Oh, the elaborate ease, to cover the
overpowering awkwardness of those former tête-à-tête meetings!
Pembroke felt this acutely when he first saw her—but it vanished
strangely at the moment that Olivia held out her little hand and spoke
to him. Her voice, her manner, were pleasantly natural. It carried him
back to the old days when he was gradually slipping into love with
her. How grateful and soothing had been her native charm as an
escape from Madame Koller’s exaggerated heroics!
“Papa will be sorry to miss you,” she said pointing him to the
easiest chair, and putting her feet comfortably on a footstool.
“Do you think you’ll like it?” asked Pembroke.
“That’s just what I was going to ask you.”
“You mustn’t ask me. You know Congressmen are received in
society only on sufferance. I exist on the borders as it were, and am
permitted to dwell there in spite of, not because I am a
Congressman.”
Olivia smiled and nodded her head.
“I know how it is,” she said, “I’ve heard.”
“Now what do you want to do first?”
“I think,” said Olivia, propping her rounded chin on her hand, “I
should like to go to a ball. I have not been to a real ball for six years
—not since we left Paris. You may be surprised at this frivolity in one
of my years—you know I am getting out of my twenties awfully fast—
but it is still a fact.”
“Your age is certainly imposing. There is a superb ball to be given
at the Russian Legation next week—the Minister is a new man—just
come. I received a card, and I can get one for you and your father
through one of the secretaries of legation who is my friend.”
Pembroke produced a handsome invitation card, bearing the
name of the Russian Minister and Madame Volkonsky.
Olivia’s eyes sparkled. She loved balls as the normal girl always
does.
“And I shall go out to-morrow morning and buy a ball gown. Shall
I have white tulle and water lilies, or peach-blow satin?”
“White, by all means,” answered Pembroke, gravely. “I like to see
women in white.”
“A white gown,” continued Olivia, reflectively, “is always safest.”
“I suppose, you will go to balls all the time after this one. It will be
like the first taste of blood to a tiger.”
“Yes, after a long period of—what do you call it—graminivorous
diet. By the way, some friends of yours came to see me to-day. The
De Peysters.”
“Yes, I like them very much. Helena is a charming little thing.”
“Delightful girl,” echoed Olivia, with much more emphasis than
the subject required.
Pembroke had only intended to pay an ordinary afternoon call,
but it was so unexpectedly pleasant sitting there with Olivia that the
fall of night and the Colonel’s return both took him unawares. The
Colonel was delighted to see him.
“This is pleasant,” cried he, standing with his broad back to the
fire, and stroking his white mustache. “I brought my riding horse up,
and Olivia’s, too, and I sent Petrarch around this morning to make a
permanent arrangement. The rogue of a livery man asked me such a
stupendous price that I was forced to send him word I didn’t desire
board for myself and my daughter included with the horses. Ah,
times are changed—times are changed! Sad lot of you in public life
now, begad.”
“Very sad lot, sir.”
“If we could only get back to Old Hickory in the White House, and
the mail twice a week from New York, brought in the stage coach—”
“And Old Hickory’s penchant for Mrs. Eaton, and half the
Congress getting tight at the White House New Year’s Day. We
ought to have it all.”
“Yes—yes—Zounds, sir, we ought to have it all!”
Then there was the ball to talk about, and presently, Pembroke
declining the Colonel’s hearty invitation to stay and dine off whatever
miserable fare a city market afforded, and try some port he had
brought from Virginia, knowing there was nothing fit to drink to be
had in Washington, he left. Olivia’s invitation to stay was rather faint
—had it been heartier, perhaps he might have remained. As it was,
he went home, and surprised Miles by coming in whistling jovially.
CHAPTER XV.
The night of the ball arrived. Olivia and her father, the De
Peysters and Pembroke had all agreed to go in one party. The De
Peysters had been very kind and attentive to Olivia. Her gentle ways
had captivated Mrs. De Peyster, and the fun innate in her had done
the same for Helena. They had asked Olivia to receive with them on
their reception day, and she had made quite a little success on her
first appearance in Washington society. She sat behind a cosy tea
table in an alcove, and poured tea with much grace. She was a good
linguist, and put two or three young diplomatists, struggling with the
English tongue, at ease by talking to them in their own language.
She possessed the indefinable charm of good breeding, never more
effective than when contrasted with the flamboyant, cosmopolitan
Washington society. The women soon found out that the men flocked
around her. She had half a dozen invitations before the day was out.
Helena, a soft, blonde, kittenish young thing, was in raptures over
her, admiring her as only a very young girl can admire and adore one
a little older than herself. Pembroke was among the later callers,
and, strange to say, Miles was with him. There were but few persons
there by that time, and these Mrs. De Peyster was entertaining in the
large drawing-room. Helena brought Miles into the little alcove and
plied him with soft speeches, tea and cakes. Pembroke and Olivia
sitting by exchanged smiles at the two enjoying themselves boy and
girl fashion. Helena was but nineteen, and Miles had not yet passed
his twenty-third birthday. The horror of his wound was added to by
the youth of his features.
“Now take this little cake,” said Helena, earnestly. “I made these
myself. Do you know that I can make cakes?”
“What an accomplished girl! I shall be afraid of you. I learned to
make ash cakes during the war,” answered Miles as gravely.
“What is an ash cake, pray?”
“Why, it’s—it’s—corn bread baked in the ashes.”
“Oh, how funny! And how do you get the ashes off?”
“Wash them off.”
In the course of the discussion Miles had quite forgotten a
piteous and ineffective little stratagem of his to turn the uninjured
side of his face toward whom he was addressing. He leaned forward,
gazing into Helena’s pretty but somewhat meaningless face, just as
any other youngster might have done, and Helena, with youthful
seriousness, had plunged into the sentimental discussion wherein
the American girl is prone to fall. Pembroke would have gone after
ten minutes, but Miles was so evidently enjoying himself, that the
elder brother stayed on. It was like the afternoon at Olivia’s house—
so home-like and pleasant—Olivia and himself keeping up a
desultory conversation while they sipped tea and listened half-
amused to the two youngsters on the other side of the round table.
Olivia glanced at the clock over the mantel—it was half-past six.
“I must go,” she said. “I shall just have time for my dinner and for
an hour’s rest before I dress for the ball.”
Mrs. De Peyster and Helena urged her to remain and dine, but
Olivia declined, and the servant announced her carriage. Pembroke
put her white burnous around her in the hall, and handed her to her
carriage. They were all to meet at the Russian Legation at half-past
ten.
At that hour the broad street in front of the Legation was packed
with carriages. An awning for the waiting footmen extended on each
side of the broad porte cochére. Half a dozen policemen kept the
carriages in line and the coachmen in order—for this was the great
ball of the season, a royal grand duke was to be present, and the
fame of Madame Volkonsky’s beauty had gone far and wide. The
vast house blazed with lights, and amid the rolling of wheels, and the
hubbub of many voices could be heard the strains of an orchestra
floating out.
Almost at the same moment the carriages containing Olivia and
her father, Pembroke and the De Peysters drove up, and the party
vanished upstairs.
“How beautiful you are!” cried Helena delightedly, up in the
dressing room, as Olivia dropped her wraps and appeared in her
dainty white toilette, Olivia blushed with gratified vanity. Her dress
was the perfection of simplicity, soft and diaphanous, and around her
milk white arms and throat were her mother’s pearls.
As the three ladies came out into the brilliant corridor to meet
their escorts, Pembroke received a kind of thrill at Olivia’s beauty—a
beauty which had never struck him very forcibly before. She was
undoubtedly pretty and graceful, and he had often admired her slight
and willowy figure—but she had grown beautiful in her solitary
country life—beautiful with patience, courage and womanliness. The
Colonel, in a superb swallow-tail of the style of ten years past, his
coat-tails lined with white satin, his snowy ruffle falling over the
bosom of his waistcoat, his fine curling white hair combed carefully
down upon his velvet collar in the old fashion, offered his arm like a
prince to Mrs. De Peyster, herself a stately and imposing matron,
and proud to be escorted by such a chevalier. Pembroke walked
beside Olivia and Helena down the broad staircase.
Is there any form of social life more imposing than a really
splendid ball? The tall and nodding ferns and palms, the penetrating
odor of flowers, the clash of music, the brilliant crowd moving to and
fro through the great drawing-rooms and halls, brought a deeper
flush to Olivia’s cheek. She felt like a débutante.
They made their way slowly toward the upper end of the last of a
noble suite of rooms. Pembroke was just saying in low tone to the
two girls, “I have looked out for your interests with the Grand Duke.
My friend Ryleief has promised to present both of you—an honor I
waived for myself, as being quite beneath the Grand Duke’s notice,
and—”
“Colonel and Miss Berkeley, Mrs. and Miss de Peyster; Mr.
Pembroke—” was bawled out by Pembroke’s friend, Ryleief who was
making the introductions to the new Minister and his wife—and the
party stood face to face with Ahlberg and Madame Koller.
The rencontre was so staggering and unexpected that Pembroke
quite lost his self-possession. He gazed stupidly at the pair before
him—M. and Madame Volkonsky, who had formed much of his life
five years before as Ahlberg and Elise Koller. He saw Ahlberg’s
breast covered with orders, and he wore an elaborate court suit.
Madame Koller, or Madame Volkonsky, blazed with diamonds. Her
hair was as blonde and as abundant as ever, and far behind her
streamed a gorgeous satin train of the same golden hue as her hair.
Olivia, too, felt that sudden shock at meeting people who rise, as
it were, like the dead from their graves. She felt also that repulsion
that came from a knowledge of both of them. She could only silently
bow as they were presented. But both M. and Madame Volkonsky
expressed more than mere surprise at the meeting. Ahlberg or
Volkonsky as he now was, turned excessively pale. His uncertain
glance fell on Pembroke, and turned again on his wife. As for her,
the same pallor showed under the delicate rouge on her cheek, but
women rally more quickly under these things than men do. Besides,
she had contemplated the possibility of meeting some of these
people, and was not altogether unprepared for it.
If, however, the blankness of amazement had seized upon Olivia
and Pembroke, and if the De Peysters were also a little unnerved by
the strangeness of what was occurring before them, Colonel
Berkeley was as cool as a cucumber. He held out his hand warmly.
He rolled out his salutations in a loud, rich voice.
“Why, how do you do Eliza. You’ll excuse an old man, my dear,
for calling you by your first name, won’t you? And my friend Ahlberg
that was. This is delightful,” he added, looking around as if to
challenge the whole party.
In the midst of the strange sensations which agitated him,
Pembroke could scarcely forbear from laughing at the Colonel’s
greeting, and the effect it produced. Madame Volkonsky flushed
violently, still under her rouge, while Volkonsky’s face was a study in
its helpless rage. Poor Ryleief, with a mob of fine people surging up
to be introduced, was yet so consumed with curiosity, that he held
them all at bay, and looked from one to the other.
“Does Madame understand that gentleman?” he asked in French,
eagerly—
“Of course she does, my dear fellow,” heartily responded Colonel
Berkeley in English. “She spoke English long before she learned
Rooshan, if she ever learned it. Hay, Eliza?”
The Colonel’s manner was so very dignified, and although jovial,
so far removed from familiarity, that Madame Volkonsky did not know
whether to be pleased by the recognition or annoyed. If, as it was
likely, it should come out that she was an American, here were
people of the best standing who could vouch at least for her origin.
She held out her hand to the Colonel, and said rapidly in French:
“I am very glad to meet you. I cannot say much here, but I hope
to see you presently.” When Pembroke made his bow and passed,
Volkonsky called up all his ineffable assurance and gave him a
scowl, which Pembroke received with a bow and a cool smile that
was sarcasm itself. Madame Volkonsky did not look at him as she
bowed, nor did he look at her.
In a moment they were clear of the press. The De Peysters were
full of curiosity.
“Who were they? Who are they?” breathlessly asked Helena.
“My dear young lady,” responded the Colonel, smoothing down
his shirt-frill with his delicate old hand, “Who they were I can very
easily tell you. Who they are, I am blessed if I know.”
While the Colonel was giving a highly picturesque account of
Eliza Peyton through all her transformations until she came to be
Elise Koller, since when Colonel Berkeley had no knowledge of her
whatever, Pembroke had given his arm to Olivia, and they moved off
into a quiet corner, where the spreading leaves of a great palm made
a little solitude in the midst of the crowd, and the lights and the crash
of music and the beating of the dancers’ feet in the distance.
Pembroke was alternately pale and red. Madame Volkonsky was
nothing to him now, but he hated Volkonsky with the reprehensible
but eminently human hatred that one man sometimes feels for
another. Volkonsky was a scoundrel and an imposter. It made him
furious to think that he should have dared to return to America, albeit
he should come as the accredited Minister of a great power. It
showed a defiance of what he, Pembroke, knew and could relate of
him, that was infuriating to his self-love. For Elise, he did not know
exactly what he most felt—whether pity or contempt. And the very
last time that he and Olivia Berkeley had discussed Madame Koller
was on that April night in the old garden at Isleham—a recollection
far from pleasant.
“Papa’s remark that this meeting was delightful, struck me as
rather ingeniously inappropriate,” said Olivia, seeking the friendly
cover of a joke. “It is frightfully embarrassing to meet people this
way.”
“Very,” sententiously answered Pembroke. He was still in a whirl.
Then there was a pause. Suddenly Pembroke bent over toward
her and said distinctly:
“Olivia, did you ever doubt what I told you that night in the garden
about Madame Koller? that she was then, and had been for a long
time, nothing to me? Did you ever have a renewal of your unjust
suspicions?”
“No,” answered Olivia, as clearly, after a short silence.
In another instant they were among the crowd of dancers in the
ball room. Neither knew exactly how they happened to get there.
Pembroke did not often dance, and was rather surprised when he
found himself whirling around the ball room with Olivia, to the rhythm
of a dreamy waltz. It was soon over. It came back to Olivia that she
ought not so soon to part company with the De Peysters, and she
stopped at once, thereby cutting short her own rapture as well as
Pembroke’s. Without a word, Pembroke led her back to where the
Colonel and Mrs. De Peyster and Helena were. Helena’s pretty face
wore a cloud. She had not yet been asked to dance, and was more
puzzled than pleased at the meeting which she had witnessed in all
its strangeness. Pembroke good naturedly took her for a turn and
brought her back with her card half filled and the smiles dimpling all
over her face.
Meanwhile, the ball went on merrily. Ryleief escaped from his
post as soon as possible and sought Pembroke.
“So you knew M. Volkonsky?” he said eagerly, in a whisper.
“Yes,” said Pembroke—and his look and tone expressed
volumes.
Ryleief held him by the arm, and whispered:
“This is confidential. I suspected from the first that our new chief
was—eh—you know—not exactly—”
“Yes,” answered Pembroke, “not exactly a gentleman. An arrant
knave and coward, in short.”
Ryleief, a mature diplomatic sprig, looked fixedly at Pembroke,
his hard Muscovite face growing expressive.
“Speaking as friends, my dear Pembroke—and, you understand
in my position the necessity of prudence—M. Volkonsky is not
unknown among the Russian diplomats. He has been recalled once
—warned repeatedly. Once, some years ago, it was supposed he
had been dismissed from the diplomatic corps. But he reappeared
about five years ago under another name—he was originally an
Ahlberg. He certainly inherited some money, married some more,
and took the name of Volkonsky—said it was a condition of his
fortune. He has been chargé d’affaires at Munich—later at Lisbon—
both promotions for him. What his power is at the Foreign Office I
know not—certainly not his family, because he has none. It is said he
is a Swiss.”
“He will not be long here,” remarked Pembroke. Then Pembroke
went away and wandered about, feeling uncomfortable, as every
man does, under the same roof as his enemy. He felt no
compunction as to being the guest of Volkonsky. The legation was
Russian property—the ball itself was not paid for out of Volkonsky’s
own pocket, but by his government. Pembroke felt, though, that
when it came out, as it must, the part that he would take in exposing
the Russian Minister, his presence at the ball might not be
understood, and he would gladly have left the instant he found out
who Volkonsky really was but for the Berkeleys and the De Peysters.
He stood off and watched the two girls as they danced—both with
extreme grace. There was no lack of partners for them. Mrs. De
Peyster, with the Colonel hovering near her, did not have her
charges on her hands for much of the time. The truth is, Olivia,
although the shock and surprise of meeting two people who were
connected with a painful part of her life was unpleasant, yet was she
still young and fresh enough to feel the intoxication of a ball. The
music got into her feet, the lights and flowers dazzled her eyes. She
was old enough to seize the present moment of enjoyment, and to
postpone unpleasant things to the morrow, and young enough to feel
a keen enjoyment in the present. She would never come to another
ball at the Russian Legation, so there was that much more reason
she should enjoy this one.
As Pembroke passed near her once she made a little mocking
mouth at him.
“Your friend, Ryleief, promised that I should be introduced to the
Grand Duke—and—”
“Look out,” answered Pembroke, laughing, “he is coming this
way. Now look your best.”
At that very instant Ryleief was making his way toward them with
the Grand Duke, a tall, military looking fellow, who surveyed the
crowd with very unpretending good humor. Pembroke saw the
presentation made, and Olivia drop a courtesy, which Helena De
Peyster, at her elbow, imitated as the scion of royalty bowed to her.
The Grand Duke squared off and began a conversation with Olivia.
She had the sort of training to pay him the delicate flattery which
princes love, but she had the American sense of humor which the
continental foreigners find so captivating. Pembroke, still smiling to
himself, imagined the platitudes his royal highness was bestowing
upon the young American girl, when suddenly the Grand Duke’s
mouth opened wide, and he laughed outright at something Olivia had
said. Thenceforth her fortune was made with the Grand Duke.
The next thing Pembroke saw was Olivia placing her hand in the
Grand Duke’s, and the pair went sailing around the room in the
peculiar slow and ungraceful waltz danced by foreigners. Olivia had
no difficulty in keeping step with her six-foot Grand Duke, and really
danced the awkward dance as gracefully as it could be done. Mrs.
De Peyster’s face glowed as they passed. Olivia was chaperoned by
her, and as such she enjoyed a reflected glory. The great maternal
instinct welled up in her—she glanced at Helena—but Helena was
so young—a mere chit—and Mrs. De Peyster was not of an envious
nature. Colonel Berkeley felt a kind of pride at the success Olivia
was making, but when a superb dowager sitting next Mrs. De
Peyster asked, in a loud whisper, if he was “the father of Miss
Berkeley,” the Colonel’s wrath rose. He made a courtly bow, and
explained that Miss Berkeley was the daughter of Colonel Berkeley,
of Virginia.
Not only once did the Grand Duke dance with Olivia, but twice—
and he asked permission to call on her the next afternoon.
“With the greatest pleasure,” answered Olivia gayly—“and—pray
don’t forget to come.”
At which the Grand Duke grinned like any other man at a merry
challenge from a girl.
At last the ball was over. Toward two o’clock Pembroke put the
ladies of his party in their carriages and started to walk home.
Madame Volkonsky had not been able to spoil the ball for Olivia.
“Good-bye,” she cried to Pembroke, waving her hand. “To-
morrow at four o’clock he comes—I shall begin making my toilette at
twelve.”
“Very pretty ball of Eliza Peyton’s,” said the Colonel, settling
himself back in the carriage and buttoning up his great-coat.
“Volkonsky—ha! ha! And that fellow, Ahlberg—by Gad! an infernal
sneaking cur—I beg your pardon, my dear, for swearing, but of all
the damned impostors I ever saw M. Volkonsky is the greatest,
excepting always Eliza Peyton.”
CHAPTER XVI.
While Olivia might wince, and the Colonel chuckle over the
Volkonsky incident, it was a more serious matter to Volkonsky. He
had certainly taken into account the possibility of meeting some old
acquaintances, but neither he nor Madame Volkonsky had cared to
keep up with events in the remote county in Virginia, where they had
passed some agitating days. Volkonsky therefore was quite unaware
that Pembroke was in Congress. The first meeting to him was an
unpleasant shock, as he had learned to fear Pembroke much in
other days. But when he began to inquire quietly about him of
Ryleief, who evidently knew him, Volkonsky’s discomfort was very
much increased. For Ryleief, who rather exaggerated the influence
of a representative in Congress, impressed forcibly upon Volkonsky
that Pembroke possessed power—and when Volkonsky began to
take in that Pembroke’s determined enmity as a member of the
Foreign Affairs Committee might amount to something, he began to
be much disturbed. Before the last guest had rolled away from the
door on the night of the ball, Volkonsky and his wife were closeted
together in the Minister’s little study. Whatever passing fancy
Madame Volkonsky might have entertained for Pembroke some
years ago, Volkonsky was quite indifferent—and if Pembroke
retained any lingering weakness for her—well enough—he might be
induced to let Volkonsky dwell in peace.
When Madame Volkonsky entered the room, her husband placed
a chair for her. Often they quarreled, and sometimes they were
reported to fight, but he never omitted those little attentions. Madame
Volkonsky’s face was pale. She did not know how much lay in
Pembroke’s power to harm them, but she was shaken by the
encounter. It was hard, just at the opening of a new life, to meet
those people. It was so easy to be good now. They were free for a
time from duns and creditors—for during her marriage to Ahlberg
she had become acquainted with both. She had a fine
establishment, a splendid position—and at the very outset arose the
ghost of a dead and gone fancy, and the woman before whom she
had in vain humiliated herself, and the man who knew enough to ruin
her husband. It was trying and it made her look weary and very old.
Volkonsky began in French:
“So you met your old acquaintances to-night.”
“Yes.”
“That charming M. le Colonel called you Eliza Peyton.”
“Yes,” again answered Madame Volkonsky.
“This comes of that crazy expedition to America which I tried to
dissuade you from.”
Madame Volkonsky again nodded. She was not usually so meek.
“And that haughty, overbearing Pembroke. Does he still cherish
that romantic sentiment for you, I wonder.”
Madame Volkonsky blushed faintly. She was not as devoid of
delicacy as her husband.
“If he does,” continued Volkonsky, meditatively, “he might be
induced—if you should appeal to him—”
“Appeal to him for what?” inquired Madame Volkonsky, rising and
turning paler. The contempt in her tone angered Volkonsky.
“Not to ruin us. That man is now in the Congress. He has to do
with foreign affairs. He hates me, and, by God, I hate him. He knows
things that may cause you to give up this establishment—that may
send us back across the water under unpleasant circumstances. You
know about the dispute at cards, and other things—you have not
failed to remind me of them,—and if Pembroke is disposed he can
use this with frightful effect now.”
Madame Volkonsky remained perfectly silent. She was stunned
by the information Volkonsky gave her—but Volkonsky was quite
oblivious of her feelings. He was gnawing his yellow mustache.
“You might see him,” he said. “You might appeal to him—throw
yourself on his mercy—”
“What a wretch you are,” suddenly burst out Madame Volkonsky
in English. They had talked in French all this time, which she spoke
apparently as well as English—but like most people, she fell into the
vernacular when under the influence of strong emotion. Volkonsky
glanced up at her.
“What is it now?” he asked, peevishly.
His wife turned two blazing eyes on him. The fact that she was
not upon a very high plane herself did not prevent her from being
indignant at his baseness—and wounded pride drove home the
thrust.
“That you should dare, that any man should dare—to propose
that a wife should work on a man’s past liking for her to serve her
husband’s ends. Ahlberg, every day that I have lived with you has
shown me new baseness in you.”
This was not the first time Volkonsky had heard this—but it was
none the less unpleasant. Also, he rather dreaded Madame
Volkonsky’s occasional outbursts of temper—and he had had
enough for one night.
“It is no time for us to quarrel—and particularly do not call me
Ahlberg. My name is now legally Volkonsky, and I would wish to
forget it ever was anything else. We should better design how to
keep this Pembroke at bay. I am sure,” continued Volkonsky
plaintively, “I have never sought to injure him. Why should he try to
ruin me for a little scene at a card table that occurred five years ago?
I wonder if that ferocious Cave will turn up soon?”
Madame Volkonsky turned and left him in disgust. In spite of her
cosmopolitan education, and all her associations, there was born
with her an admiration for Anglo-Saxon pluck which made her
despise Volkonsky methods. The idea of scheming and designing to
placate a man who had caught him cheating at cards filled her with
infinite contempt.
In the course of the next few days, Madame Volkonsky was
deeply exercised over the influence that Pembroke would have upon
her future. She had talked their affairs over often with her husband in
those few days. He had not failed to convey to her the rather
exaggerated impression that he had received from Ryleief, as to
Pembroke’s power to harm.
One afternoon, when Volkonsky and his wife were driving in their
victoria, they passed the Secretary of State’s carriage drawn up to
the sidewalk. Pembroke was about to step into it. The Secretary
himself, a handsome, elderly man, was leaning forward to greet him,
as Pembroke placed his foot on the step. Madame Volkonsky looked
at her husband, who looked blankly back in return. The Secretary’s
carriage whirled around, and both gentlemen bowed—the Secretary
to both the Minister and his wife, Pembroke pointedly to Madame
Volkonsky.
Volkonsky turned a little pale as they drove off.
“I wonder if the Secretary will ever speak to us again,” said
Madame Volkonsky, half maliciously.
Yet it was as much to her as to him. It would indeed be hard were
they driven in disgrace from Washington. Volkonsky had been
surprisingly lucky all his life, but luck always takes a turn. Now, his
recall as Minister would be of more consequence than his
escapades as attaché or Secretary of Legation. Then, he had played
wild works with her fortune, such as it was. Madame Volkonsky’s
thoughts grew bitter. First had come that struggle of her girlhood—
then her artistic career—ending in a cruel failure. Afterward the
dreadful years of life tied to Koller’s bath chair—followed by her
stormy and disappointed widowhood. This was the first place she
had ever gained that promised security or happiness—and behold!
all was likely to fall like a house of cards.
They paid one or two visits, and left cards at several places.
Madame Volkonsky had imagined that nothing could dull the
exquisite pleasure of being a personage, of being followed, flattered,
admired. She found out differently. The fame of her beauty and
accomplishments had preceded her. Everywhere she received the
silent ovation which is the right of a beautiful and charming woman—
but her heart was heavy. At one place she passed Olivia and her
father coming out as they were going in. Olivia, wrapped in furs,
looked uncommonly pretty and free from care. As the two women
passed, each, while smiling affably, wore that hostile air which ladies
are liable to assume under the circumstances. The Colonel was all
bows and smiles to Madame Volkonsky as usual, and refrained from
calling her Eliza.
Nor did the presence of the Volkonskys in Washington conduce
to Olivia’s enjoyment although it certainly did to her father’s. The
Colonel was delighted. In the course of years, Eliza Peyton had
afforded him great amusement. He was a chivalrous man to women,
although not above teasing Madame Volkonsky, but he refrained
from doing what poor Elise very much dreaded he would—telling of
her American origin. She had admitted that her mother was an
American—an admission necessary to account for the native,
idiomatic way in which she spoke the English language, and Colonel
Berkeley knowing this, did not hesitate to say that in years gone by,
he had known Madame Volkonsky’s mother, and very cheerfully bore
testimony to the fact that the mother had been of good family and
gentle breeding. So instead of being a disadvantage to her, it was
rather a help. But Olivia and herself were so distinctly antipathetic
that it could scarcely fail to produce antagonism. And besides her
whole course about Pembroke had shocked Olivia. Olivia was
amazed—it was not the mere difference of conduct and opinion—it
was the difference of temperament. Remembering that Madame
Volkonsky had at least the inheritance of refinement, and was quite
at home in the usages of gentle breeding, it seemed the more
inexcusable. In all those years Olivia had been unable to define her
feelings to Pembroke. She could easily have persuaded herself that
she was quite indifferent to him except that she could not forget him.
It annoyed her. It was like a small, secret pain, a trifling malady, of
which the sufferer is ashamed to speak.
Not so Pembroke. The love that survives such a blow to pride
and vanity as a refusal, is love indeed—and after the first tempest of
mortification he had realized that his passion would not die, but
needed to be killed—and after five years of partial absence,
awkward estrangement, all those things which do most effectually kill
everything which is not love, her presence was yet sweet and potent.
The discovery afforded him a certain grim amusement. He was
getting well on in his thirties. His hair was turning prematurely gray,
and he felt that youth was behind him—a not altogether unpleasant
feeling to an ambitious man. Nevertheless, they went on dining
together at the Berkeleys’ own house, at the De Peysters’, at other
places, meeting constantly at the same houses—for Pembroke went
out more than he had ever done in Washington before, drawn subtly
by the chance of meeting Olivia—although where once she was cool
and friendly, she was now a little warmer in her manner, yet not
wholly free from embarrassment. But neither was unhappy.

ebook download (eBook PDF) Database Processing Fundamentals, Design, and Implementation, 15th Edition all chapter

Uploaded by

Copyright:

Available Formats

You might also like

ebook download (eBook PDF) Database Processing Fundamentals, Design, and Implementation, 15th Edition all chapter

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ebook download (eBook PDF) Database Processing Fundamentals, Design, and Implementation, 15th Edition all chapter

Uploaded by

Copyright:

Available Formats

(eBook PDF) Database Processing

Fundamentals, Design, and

(Original PDF) Database Processing: Fundamentals,

Database Processing: Fundamentals, Design, and

Database Principles: Fundamentals of Design,

Database Systems: Design, Implementation, Management

Database Systems: Design, Implementation, & Management

(eBook PDF) Materials: Engineering, Science, Processing

(eBook PDF) Operations Strategy: Design, Implementation

(eBook PDF) Database Design Application Development

SQL Enhancements for Querying a Single Table 66

PART 2 ■ Database Design 145

Chapter 3: The Relational Model and Normalization 146

Chapter 4: Database Design Using Normalization 191

Chapter 5: Data Modeling with the Entity-Relationship Model 212

A01_KROE2749_15_SE_FM.indd 6 14/12/17 4:03 PM

The Entity-Relationship Model 213

Chapter 6: Transforming Data Models into Database Designs 267

PART 3 ■ Database Implementation 323

Chapter 7: SQL for Database Construction and Application

A01_KROE2749_15_SE_FM.indd 7 14/12/17 4:03 PM

Managing Table Structure with SQL DDL 327

Chapter 8: Database Redesign 424

PART 4 ■ Multiuser Database Processing 453

Chapter 9: Managing Multiuser Databases 454

A01_KROE2749_15_SE_FM.indd 8 14/12/17 4:03 PM

Concurrency Control 457

Chapter 10: Managing Databases with Microsoft SQL Server 2017,

ONLINE CHAPTER: SEE PAGE 495 FOR INSTRUCTIONS

A01_KROE2749_15_SE_FM.indd 9 15/12/17 4:00 PM

ONLINE CHAPTER: SEE PAGE 495 FOR INSTRUCTIONS

A01_KROE2749_15_SE_FM.indd 10 15/12/17 4:00 PM

Oracle Database Concurrency Control

ONLINE CHAPTER: SEE PAGE 495 FOR INSTRUCTIONS

PART 5 ■ Database Access Standards 497

Chapter 11: The Web Server Environment 498

A01_KROE2749_15_SE_FM.indd 11 14/12/17 4:03 PM

The Microsoft .NET Framework and ADO.NET 512

Chapter 12: Data Warehouses, Business Intelligence Systems,

ONLINE APPENDICES: SEE PAGE 620 FOR INSTRUCTIONS

A01_KROE2749_15_SE_FM.indd 12 14/12/17 4:03 PM

How Do I Create a New Microsoft Access 2016 Database?

Appendix B: Getting Started with Systems Analysis and Design

Appendix C: E-R Diagrams and the IDEF1X and UML Standards

A01_KROE2749_15_SE_FM.indd 13 14/12/17 4:03 PM

How Does UML Represent Entities and Relationships?

Appendix D: Getting Started with Microsoft Visio 2016

Appendix E: Getting Started with the MySQL Workbench

Appendix F: The Semantic Object Model

A01_KROE2749_15_SE_FM.indd 14 15/12/17 1:40 PM

Appendix G: Physical Database Design and Data Structures for

A01_KROE2749_15_SE_FM.indd 15 14/12/17 4:03 PM

Why Is XML Important?

Appendix J: Business Intelligence Systems

Appendix K: Big Data

Appendix L: JSON and Document Databases

A01_KROE2749_15_SE_FM.indd 16 14/12/17 4:03 PM

We Didn’t Know What We Were Doing

A01_KROE2749_15_SE_FM.indd 17 14/12/17 4:03 PM