Buy Used
CDN$ 1.00
+ CDN$ 6.49 shipping
Used: Very Good | Details
Sold by wobcanada
Condition: Used: Very Good
Comment: The book has been read, but is in excellent condition. Pages are intact and not marred by notes or highlighting. The spine remains undamaged.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Databases and Transaction Processing: An Application-Oriented Approach Hardcover – Jul 24 2001

3.6 out of 5 stars 5 customer reviews

See all 2 formats and editions Hide other formats and editions
Amazon Price
New from Used from
"Please retry"
CDN$ 61.30 CDN$ 0.79

Unlimited FREE Two-Day Shipping for Six Months When You Try Amazon Student
click to open popover

No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Product Details

  • Hardcover: 1056 pages
  • Publisher: Pearson; 1 edition (July 24 2001)
  • Language: English
  • ISBN-10: 0201708728
  • ISBN-13: 978-0201708721
  • Product Dimensions: 23.7 x 19.5 x 4.4 cm
  • Shipping Weight: 1.8 Kg
  • Average Customer Review: 3.6 out of 5 stars 5 customer reviews
  • Amazon Bestsellers Rank: #709,183 in Books (See Top 100 in Books)
  •  Would you like to update product info, give feedback on images, or tell us about a lower price?

  • See Complete Table of Contents

Product Description

From the Back Cover

"This is a great book! This is the book I wish I had written."
—Jim Gray, Microsoft Research, recipient of 1998 A.M. Turing Award "for seminal contributions to database and transaction processing research"

Databases and Transaction Processing provides a complete and clear explanation of the conceptual and engineering principles underlying the design and implementation of database and transaction processing applications. Rather than focusing on how to implement the database management system itself, this text focuses on how to build database applications. To provide a solid foundation for these principles, the book thoroughly covers the theory underlying relational databases and relational query languages.

To illustrate both database and transaction processing concepts, a case study is carried throughout the book. The technical aspects of each chapter applied to the case study and the software engineering concepts required to implement the case study are discussed.

In addition to the more traditional material -- relational databases, SQL, and the ACID properties of transactions -- the book provides in-depth coverage of the most current topics in database and transaction processing technologies, including:

  • Embedded SQL, SQL/PSM, ODBC, JDBC, and SQLJ
  • Object and object-relational databases, including SQL:1999, ODMG, and CORBA
  • XML and document processing on the Web
  • Triggers and Active Databases
  • OLAP and Data Mining
  • Distributed Databases
  • TP Monitors and how they implement the ACID properties
  • Concurrency controls at different isolation levels
  • Security and Internet commerce

For more information about Addison-Wesley Computer Science books visit

Excerpt. © Reprinted by permission. All rights reserved.

Database and transaction processing systems occupy a central position in our information-based society. Virtually every large system with which we interact in our daily lives has a database at its core. The systems range from those that control the most trivial aspects of our lives (e.g., supermarket checkout systems) to those on which our lives depend (e.g., air traffic control systems). Over the next decades, we will become increasingly dependent on the correctness and efficiency of these systems.

We believe that every computer scientist and information systems professional should be familiar with the theoretical and engineering concepts that underlie these systems. These are the people who will be designing, building, maintaining, and administering these highly complex systems.

This book is intended to be a text for any of the following courses in a computer science or technically oriented information systems curriculum:

  • An introductory undergraduate or graduate course in databases
  • An undergraduate or graduate course in transaction processing for students who have had an introductory course in databases
  • An advanced undergraduate or a first graduate course in databases for student who have had an introductory course in databases

If only one course is to be taught covering both databases and transaction processing, the instructor can select material related to both topics.

Rather than focusing on how to build the database management system itself, our approach focuses on how to build applications. We believe that many more students will be implementing applications than will be building DBMSs. We believe that placing databases in the context of transaction processing accentuates this emphasis, since transactions provide the mechanism that applications use to access databases. Furthermore, we include substantial material describing the languages and APIs used by transactions to access a database, such as embedded SQL, ODBC, and JDBC.

While the book thoroughly covers conventional topics—relational databases, SQL, and the ACID properties of transactions—if also provides a very substantial treatment of less conventional and newer issues, such as object and object relational databases, XML and document processing over the Internet, and the transaction4 issues related to Internet commerce.

Although we cover many practical aspects of database and transaction processing applications, we are primarily concerned with the concepts that underlie these topics rather than on the details of particular commercial systems or applications. Thus, in the database portion of the book, we concentrate on the concepts underlying the relational and object data models rather than on any particular commercial DBMS. These concepts will remain the foundation of database processing long after SQL is obsolete. (Recall the generation of programmers who were trained in COBOL and found it extremely difficult to learn any other language.) In a similar way, in the transaction processing portion of the book, we concentrate on the concepts underlying the ACID properties and the technical issues involved in their implementation, rather than on any particular commercial DBMS or TP monitor.

To enhance students' understanding of the technical material, we have included a case study of a transaction processing application, the Student Registration System, which is carried through the book. While a student registration system can hardly be considered glamorous, it has the unique advantage that all students have interacted with such a system as users. More importantly, it turns out to be a surprisingly rich application, so we can use it to illustrate many of the issues in database design, query processing, and transaction processing.

A unique aspect of the book is a presentation of the software engineering concepts required to implement transaction processing applications, using the Student Registration System as an example. Since the implementations of many information systems fail because of poor project management and inadequate software engineering, we feel that these topics should be an important part of the student's education. Our treatment of software engineering issues is brief, as many students will take a separate course in this subject. However, we believe that they will be better able to understand and apply that material when they see it presented in the context of an information system implementation. Since the courses that use this text at Stony Brook are not software engineering courses, we do not cover this material in class. Instead, we ask the students to read it and require that they use good software engineering practice in their class projects. We do cover in class those aspects of the Student Registration System that illustrate important issues in databases and transaction processing.


There is sufficient material in the book for three one-semester courses. The first half of the book is a text for a first course on databases. For students who have completed such a course, the second half of the book concentrates on transaction processing and advanced topics in databases. At Stony Brook, we offer both an undergraduate (introductory) and a more advanced (graduate) database course as well as an undergraduate and graduate version of the transaction processing course.

The book is divided into parts so that the instructor can more easily organize the material. We have included a Chapter Dependency Chart to make it easier to design customized courses.

Part I: Introduction
Chapters 1 through 3 contain introductory material for a first course in databases. Chapter 1 serves as general introduction. Chapter 2 briefly covers SQL and the ACID properties of transactions. By introducing this basic material early, we are able to remove some constraints on the order of presentation of topics discussed later.

Chapter 3 begins our discussion of the Student Registration System and the software engineering concepts appropriate for its implementation. In particular, we discuss requirements and specification documents and the use of application generators to design graphical user interfaces. In the introductory database course at Stony Brook, we ask the students to read this material but do not cover it in class lectures. However, at this point in the course, we start the class project by asking students to write a Specification Document.

Part II: Database Management
Chapters 4 through 15 constitute the core of a first course in databases. Some of the topics covered are:

  • The concept of a relation and the DDL features of SQL, including automatic constraint checking
  • The Entity-Relationship Model and schema design, including methods (and their limitations) for converting E-R diagrams to relational schemas
  • Relational algebra, calculus, and the DML features of SQL with particular attention to the semantics of complex SQL queries through relational algebra and calculus
  • Functional dependencies and normalization, including algorithms for decomposing a schema into 3NF, BCNF, and 4NF
  • Triggers and active databases, including triggers in SQL:1999
  • The inclusion of SQL statements in a program written in a conventional programming language, including embedded SQL, dynamic SQL, ODBC, JDBC, and SQLJ. The recently standardized language for stored procedures, SQL /PSM, is also discussed
  • Physical organization of the data and indexing, including B+ trees, ISAM, and hash indices
  • Query processing and optimization, including algorithms for computing selections and joins, and methods for estimating the cost of query plans

Software engineering issues, as applied to the Student Registration System, are integrated throughout these chapters. In Section 5.7, we present the database design for the system, including the E-R Diagram and relation schema. Chapter 12 presents material on Design Documents, Test Plan Documents, and project planning that is needed to complete the system. In Section 12.6, we present the detailed design and part of the Java/JDBC program for one of the transactions in the system.

Chapter 15 summarizes some of the material on transaction processing from later chapters. It can be used to enrich a database course if time permits.

Part III: Advanced Topics in Databases
Chapters 16 through 19 contain materials that can become part of an advanced database course. Such a course includes all the chapters in this part plus Chapter 27. In our experience, lack of time prevents one or more sections of Chapters 7, 8, 9,10, 11, and 14 from being covered in a first database course, so this material can also be included. The topics covered in Part III include

  • Object and object-relational databases, including the conceptual model, ODMG databases, object-relational extensions of SQL:1999, and CORBA
  • Database aspects of document processing on the Web, including a detailed discussion of XML Schema, XPath, XSLT, and XQuery
  • Distributed databases, including heterogeneous and homogeneous systems, multidatabases, fragmentation, semijoins, global query optimization, query design, and distributed database design
  • Online analytic processing and data mining, including star schemas, the CUBE and ROLLUP operators, associations, and classification

Part IV: Transaction Processing
Chapters 20 through 27, together with portions of Chapters 9 and 10, contain material for a one-semester course in transaction processing. Many of the examples in these chapters refer to the Student Registration System design developed in Chapters 3 and 12 and in Section 5.7. We ask the students to read this material as appropriate.

Chapter 20 contains a detailed description of the ACID properties of transactions. Chapters 21 and 22 describe a variety of transaction models and the architecture of transaction processing systems in a distributed and heterogeneous client/server environment. Some of the topics covered are

  • Models of transactions, including savepoints, chained transactions, transactional queues, nested and multilevel transactions, distributed transactions, multidatabase systems, and workflow systems
  • Architectures for transaction processing systems, including, client-server organizations for both centralized and distributed databases, two-tiered and three-tiered architectures, TP monitors, and transaction managers. Transactional remote procedure call and peer-to-peer communication together with their use in organizing a transaction processing system are discussed
  • Implementation of transaction architectures and models in transaction processing applications on the Internet

Chapters 23 through 26 describe how the ACID properties of atomicity, isolation, and durability are implemented in both centralized and distributed systems. Some of the topics covered are

  • Concurrency controls for abstract databases, including strict two-phase locking, optimistic concurrency controls, timestamp-ordered concurrency controls, concurrency controls for object databases, and locking protocols to implement the different models of transactions
  • Concurrency controls for relational databases, including locking protocols for the different isolation levels, examples of correct and incorrect schedules at each isolation level, granular locking, index locking, and multiversion concurrency controls, including SNAPSHOT isolation
  • Logging and recovery, including write-ahead logs, dumps, and checkpoints
  • Distributed transactions, including the two-phase commit protocol, global serialization, global deadlocks, and synchronous and asynchronous algorithms for managing replicated data

Chapter 27 covers security and Internet commerce. Some of the topics covered are

  • Symmetric and asymmetric encryption, digital signatures, blind signatures, and certificates
  • The Kerberos protocol for authentication and key distribution
  • Internet protocols, including the SSL Protocol for authentication and session encryption, the SET Protocol for secure transactions, electronic cash protocols, and protocols that guarantee goods atomicity, certified delivery, and money atomicity

Our goals in Chapters 20 through 27 are

  • To make students aware of the architecture of the transaction processing systems with which their transactions must interact, so that they can better evaluate the features offered by competing system vendors
  • To describe the costs, measured in system resources and performance, involved in implementing the ACID properties of transactions
  • To describe techniques to decrease these costs—for example, granular locks, indices, denormalization, and table fragmentation.
  • To describe situations in which an application twill execute correctly even though isolation is not total-for example, transactions that might execute correctly at an isolation level less stringent than SERIALIZABLE

We have also included an Appendix, which covers certain system issues that are important for understanding parts of the text. These include the ideas behind modular systems and encapsulation, the basics of the client/server architecture, multiprogramming and threads, and the basics of interprocess communication. Instructors might choose to present some of this material if the students have not covered it in previous courses.


To help instructors tailor the material to the needs of their courses, we have identified certain sections that can be skipped without disrupting the flow of material in the corresponding chapters. Such sections are marked with an asterisk. Even though material covered in these sections is sometimes referenced in other chapters, these references can be ignored. In addition, exercises that are more difficult than the rest are marked with one or two asterisks, depending on the difficulty.

The text can be used in a number of different ways depending on the goals of the course. To provide some guidance to the instructor, the table on the next page shows the chapters that might be included in five different courses that address different student populations and attempt to emphasize different aspects of the subject. In this table, "yes" means that all parts of the chapter should be covered by the lectures. "Parts" means that the instructor can select only parts of the material presented in the chapter. "Read" means that the chapter can be given as a reading assignment to the students.

Column 1 marks chapters that would be covered in a slow-paced introductory database course. In such a course, for instance, only parts of Chapter 8 on normalization theory might be included—perhaps only the introductory sections. Similarly, only some parts of Chapter 10, on various ways in which SQL can be combined with a host language, might be covered-perhaps only one approach, the one required for the course project.

Columns 2 and 3 outline two more intensive introductory database courses. Column 2 expands the material covered in the introductory course in the direction of database applications, while Column 3 describes a more theory-oriented version of the course. It provides a more in-depth coverage of the normalization theory, foundations of query languages, and query optimization at the expense of the application-oriented material in Chapter 10. Although we have characterized this material as theory-oriented, we might also have characterized it as system-oriented, because it covers issues involved in the design of a DBMS. The courses in these two columns are the ones we teach in our undergraduate program at Stony Brook (depending on the interests of the instructor).

Column 4 describes an advanced database course. The course might start by reviewing or filling in material that the instructor judges the students might not have covered in a prerequisite, introductory database course. Such material would probably be found in Chapters 7, 8, 9, 10, and 14. The body of the course then continues with advanced database topics and some material on transactions in electronic commerce. At Stony Brook this course is taught to graduate students who had a database course in their undergraduate years.

Column 5 describes a course on transaction processing that also assumes that students have had an introductory database course as a prerequisite. At Stony Brook, we teach both an undergraduate and a graduate version of this course. The material on transaction processing is supplemented with related material that might not have been covered in the student's prerequisite database course, for, example, some material from Chapters 9 and 10.

For further fine-tuning of courses, the chapter dependency diagram that follows can be of help. The figure identifies two kinds of dependencies. Solid arrows indicate that one chapter depends on much of the material presented in another chapter, except for the sections marked as optional. Dotted arrows indicate weak dependency, which means that only a few concepts developed in the prerequisite chapter are used in the dependent chapter, and those concepts can be covered quickly. The dependencies involving Chapter 27 are a special case. It can be taught either at the end of a transaction processing course, in which case it depends on Chapters 21, 22, and 25, or at the end of a database course, in which case it depends on Chapter 15.


In addition to the text, the following supplementary materials are available to assist instructors:

  • Online PowerPoint presentations for all chapters
  • Online PowerPoint slides of all figures
  • An online solution manual containing solutions for the exercises
  • Any additional references, notes, errata, homeworks, exams, and so forth, that we think might be of interest to oar readers

For more information on obtaining these supplements, please check online information for this book at . The solutions manual and PowerPoint presentations are available only to instructors through your Addison-Wesley sales representative.

Customer Reviews

3.6 out of 5 stars
Share your thoughts with other customers

Top Customer Reviews

Format: Hardcover
Database and Transaction Processing by Philip M. Lewis, et al. is written as a multi-purpose textbook and practical reference guide for software engineers. One can use this book both as an undergraduate introductory course in database theory and design, as an advanced graduate-level course in databases, or as a graduate level course in transaction processing.
Being outside of the academia, but still needing a foundational theoretical (but not necessarily formal or overly detailed) reference, I was impressed on the ability of the authors to present concise and useful practical facts. Some other textbooks suffer from overwrought attention to topics in database normalization, correctness proves, and such - this one gives a lot of practical advise in optimization, distributed databases and issues of concurrency control and transaction processing. Chapters are organized in a self-contained fashion, so with a bit of background in databases, reader can just read a chapter in isolation if she is interested in a topic.
In summary, a very useful book.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Hardcover
First I need to explain my background: I only knew a little about databases and SQL in general, but I knew the topic was rather complex and very broad. Since I wanted to understand how transactions are implemented I decided to find a book on them and stumbled upon this book; I am glad I did.
Do I now understand how transactions are implemented? Not 100%, but certainly a great deal more so than before I read this books' chapters on transactions. Indeed, I am far more equiped to work with transactions because this book helped me understand what is going on "under the hood". While it wasn't "code level" details, it certainly satisfied this novices' thirst for a general understanding of transaction implementation plus it piqued my curiousity to go on and learn more about transactions as written by the likes of Gray.
Further, I have been given a nice introduction to Database Theory and the topic of Entity Relationships - an entire study of how best to design our data, which before hand I was completely unaware of!
Two chapters seemed rather difficult and one of the authors was kind enough to suggest I study Susanna Epp's fine "Discrete Mathematics with Applications" before heading back into foray of DB theory.
So, all and all, I found this book a delight and well worth working through.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
Format: Hardcover
At first glance, this might seem like a good textbook. However, after having to deal with it for 3/4 of a semester, I've learned to not judge a book by its cover.
First of all, formulas are not presented in a way that is helpful. Facts should be highlighted and processes explained more clearly and concisely. As a non-programmer (I've taken web programming, computer science 1 and 2 up through binary trees), I felt that the symbols used for representing a lot of the rules were more confusing, and the text didn't help much in the explanation of what these combinations of symbols actually represented. Luckily I had a friend who could help me sum up what these things meant!
Our instructor also posted solutions to the problems from the instructor's book. One week there were 5 corrections for 10 homework problems (where the meat of the problem was actually approached in the WRONG WAY). Not to mention the multiple typos that any spell checker could have found.
For $[money], I'm sure there's a better textbook out there. To quote one of my friends, there is a better interpretation of Jim Gray's quote:
"This is a great book!" (I didn't read it at all!)
"This is the book I wish I had written!" (Then it wouldn't be so messed up and I'd be rolling in the dough!)...
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
By A Customer on May 22 2004
Format: Hardcover
I have had to use this book and taken the class of one of the professors who wrote it. For the first few chapters the book is ok. It quickly goes downhill from there. Gives the feeling that they started out with a lot of enthusiasm for writing it but then got bored and just tried to get it done without any real thought on how to educate a reader.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse
By A Customer on Oct. 12 2001
Format: Hardcover
Talk about credibility...Jim Gray, who won the 1998 Turing Award for his work in database and TP, is quoted on the back cover saying "This is a great book. This is the book I wish I had written."
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again.
Report abuse