Introduction to Database Systems

by C.J. Date

Book Overview

An Introduction to Database Systems vol 2. C.J. Date. Copyright 1983, Addison-Wesley, Reading, Mass. Hardcover in very good condition. Binding is secure, cover and spine are clean with minimal wear.... This description may be from another edition of this product.

• Format: Hardcover
• Language: English
• ISBN: 0201144743
• ISBN13: 9780201144741
• Release Date: January 1983
• Publisher: Addison Wesley Publishing Company
• Length: 383 Pages
• Weight: 1.45 lbs.
• Dimensions: 0.8" x 6.6" x 9.5"

Customer Reviews

An indispensible text for serious practioners

This is not a how-to, it is a how-to-understand. I own multiple editions of this book starting with the 3rd, when many of the examples referred to RBase. It won't tell you, with simple color diagrams and cut-and-paste examples, how to optimize your Oracle SQL queries or tune your DB/2 engine, but it will teach you the underlying principles of relational databases, from which the serious professional will be able to extrapolate. If you have the intelligence and stomach for it and you actually read it, it will serve you much better than the SQL in 24 hours picture books that some reviewers seem to be looking for -- it is a timeless and effective conceptual work on the subject that spans the evolution of commercial product implementations. Dilitantes and desperadoes, head for the Dummies aisle -- this one's not for you.

An Introduction for Software Engineers, not Users

Sorry, no full-color graphics, and no included disk full of fill-in-the-blank examples and wizards to build your contact list. This is an old-fashioned academic tome, not a how-to book or thinly-disguised marketing tool for some commercial database system.I suppose the biggest criticism I could make of this book is that it overestimates the target audience. Unfortunately, many who see the title of this book assume that it will teach them how to work with current database products such as Oracle, or maybe SQL Server and Access. No, this book doesn't show you how to create an invoicing system for your bicycle shop, or a web content management system. What it will show you is the conceptual underpinning of the relational data model, how to understand relational database systems in general (not everything is SQL, you know), and provide some heavy insight into how relational databases should be designed.In that sense, it can be considered an "introductory" book for software engineers, who might themselves create a new database management system. It can also be considered introductory for database administrators and systems programmers who are looking to expand their knowledge beyond the product-specific practical methods they have been exposed to. In other words, if you just want to know "how things are done" in your industry, don't read this book. If you want some insights into how things COULD be done much better, you might want to read this book.So, while I might not recommend this book to a junior programmer tasked with creating his/her first web-based ordering system, I might recommend it to the company DBA or systems architect. Even more, I would recommend this book to anyone studying C/C++, and looking to start a career in software engineering, possibly to help create new database systems. This book doesn't discuss specific implementation in C++ or anything like that but it provides an excellent target feature set and language spec for development, as well as a clarification of the formal logic behind relational database management.

A Long Shef Life

This is the best technical book I have ever read (and I have read many). This book was required for a graduate school database class at Carnegie Mellon. Although I read the class required chapters, I found little time to really read the book while in school. Since graduation (I am now a consultant) I have returned to this book constantly. It is the perfect text for those who want a solid and analytical background in the subject of relational databases. I have spoken with other classmates from CMU who feel it is the most valuable book they have. C. J. Date, one of the leaders in this field, covers relational theory, relational algebra and calculus, database design, ERD's, as well as SQL. I would encourage readers to set up the sample SUPPLIER-ORDERS-PARTS database to really leverage the examples used in the text. This book will have a longer life than any other technical book you ever purchase. A must have.

An EXCELLENT theoretical treatment

An introduction to Database systems is an excellent work and to call this work an introduction is misleading (Date explains in the preface why he chose to call it an introduction). The work is theoretically extremely dense and it requires a lot of effort to fully understand all the concepts that Date treats really exhaustively throughout the book. The book gives in-depth insight into database design concepts and it breaks every term and concept down to the bone.The style in wich the book is written makes for pleasant reading and Date's use of the English language is brilliant. Date is certainly a master of database theory and I can recommend this book to everybody who is serious about the underlying concepts of the relational database model. As an academical textbook - this book is not intended for undergraduate study but for post-graduate study it is a winner.If there is one thing that I can complain about it is that the book sheds too few light on the theory of database optimization. I hope that the 8th Ed. will also cover this topic more extensively.

Excellent, if textually dense ACADEMIC textbook

(Note this review applies to the sixth edition of this book).If you wish to quickly jump into database design without a full and rigorous knowledge of database theory (by no means a bad thing) then this book is not for you. If, however, you want a thorough grounding in the principles and practice of database theory considered from an academic standpoint, then this book is highly recommended.Date is one of the giant figures of relational database theory, and this masterful work covers, in exhaustive detail, all the elementary principles of the subject. The book commences with an overview of database systems and management, before moving on to introduce the relational model. Part II of the book covers in great detail the relational model, introducing the relational algebra and the relational calculus (and then showing the formal equivalence of the two). The SQL language is introduced.Part III discusses database design, with special emphasis on the vital topics of nonloss decomposition, functional dependencies and normalisation. For practical database designers this is perhaps the most valuable part of the book. Part IV covers data protection from the standpoints of integrity and implementation in practical systems.Part V gathers a miscellany of related topics such as optimization of queries, a discussion of the 'NULL' problem and an introduction to ditributed (i.e. client/server) database systems. Part VI is an introduction to object-oriented database systems, with an examination of the problems faced by traditional relational systems when faced with object-oriented problems.It is important to note the target audience for this book. This book is first and foremost academic by nature. Rigour is not sacrificed for conciseness or simplicity. It is textually dense, especially parts II and III (far and away the most important parts). The reader will have to put in a lot of work to fully grasp the details of the concepts. For example, Date's definition of third normal form (3NF): "A relation is in 3NF if and only if it is in 2NF and every nonkey attribute is nontransitively dependent on the primary key". To appreciate in detail the significance of this definition requires substantial effort. However, this effort will pay dividends when the time comes to actually design a real-world system. Failure to understand the principles of database theory at this level of rigour lies behind many failed implementation attempts. Not every database designer needs this knowledge, but a manager of a large database project certainly does. I would not recommend this book as an introductory text for an undergraduate course in database design, due to the large quantity of material covered and its highly theoretical exposition. I would, however, strongly recommend it for students at a higher level, professional database designers and implementors of database management systems.