An Accessible, Up-to-Date Introduction to Database Systems Database Systems, Second Edition provides a strong foundation in good design practice. Using an accessible, step-by-step approach, students will master a database methodology. Then, the authors apply this methodology to worked examples so students learn to design and build applications using a leading commercial database system. Also, a central, realistic case study is integrated throughout the text to provide an understanding of the issues involved. This new edition will build on the clear, accessible presentation of the successful first edition. New to the Second Edition
Includes additional and simplified examples.
Features new material on distributed databases including interactions with web-based data. Contains new material on object-oriented databases that covers the latest ODBM standards. Illustrates concepts with screen shots from Access(tm). Offers new coverage of query processing and optimization, data mining, data warehouses, multimedia databases, and the Internet.
- This book opened the doors of relational database management systems to me. Prior to reading it I had some general experience with MySQL but an incomplete understanding of the subject. Much to my surprise I found I really liked working with a RDBMS’s so I began searching for a book that would give me a solid introdcution to the theory and practice. I think this book fit the bill. After reading it I was ready to tackle a data migration project from Unify to Informix. Now I work as a database programmer. I have since purchased and read other RDBMS books about Informix (the RDBMS I have worked most with) but I find that I still refer to this text from time to time to clear up some minor points of confusion. This book will not make you an expert with RDBMS’s but it will give you the background necessary to build up your confidence so you can tackle other tasks. At times the prose can be a bit drawn out but those sections are few and far between. Be advised though that this book uses conceptual/practical approach to database design. While it provide some examples using MS Access and Oracle I find the conceptual discussions more interesting and indeed more useful. With this foundation I was able to begin working with Informix Dynamic Server-an RDBMS that is clearly not the focus of this book.
- This was the required textbook for a MS Predictive Analytics program. Let me start by saying this is not a “How to…” book, it is a comprehensive (yet shallow) overview of database systems from design to usage.
Here are my key concerns:
1. Content: There is too much fluff in early chapters regarding the history of database development and the shortcomings of the different models. It is interesting, but not of much practical value.
Additionally, I feel the chapters on SQL syntax and keywords lacked any kind of “Let’s put this all together” development that was a positive aspect of the ER modeling chapters. As a coding book, it falls short of other texts on the market; but, that is likely not the book’s intent.
2. Usability: The book likes to present a case study and use that as the basis for subsequent chapter discussions. The issue with this, and this is my personal pet peeve with many textbooks, is that the book references figures and paragraphs from previous chapters in subsequent chapters. What this means is that you are continually searching previous chapters’ information to understand the implementation being discussed in the current chapter (For example, a discussion on B-C Normal Form might reference the 2NF and 3NF tables from 40 pages before.). It makes for a lot of searching and bookmarking.
Overall, the book is a good effort by the authors and you can see the time that was put into it. They have a commanding knowledge of the subject, without a doubt. But the book paints with too broad a brush. It seems that some very useful information was omitted for the sake of page count. My recommendation is that the editors remove the historical aspects and include more SQL implementation.
- The book is very wordy, but vague. It should not take 1200 or so pages to explain it’s contents. The book does not readily get to the point. The chapters on SQL were very poorly written. The syntax for commands were not adequately explained and were horribly intertwined in the examples, such that it was difficult to derive the real syntax for individual clauses and commands. Chapters on modeling the database via ER and EER were also vague and written very poorly. Examples throughout the book used coincidental values and scenarios that mask out the true nature of the concepts being proposed. The author should have taken the time to put in “meaningful” examples. The exercises at the end of each chapter do not define the scope of questions being asked. They are too open ended. If it were not a requirement that I use this book, I would not waste my money on it! I could have written a better book!
- This review is for the Kindle etextbook version. The authors refer repeatedly to the appendices to learn some of the topics (or brush up on things they expect you to already know), but most of the appendices are on-line and require an access code that only comes with the paperback text. You can purchase access to the codes online, but it negates any savings you make by purchasing the etextbook. Also, you can only download the textbook to two devices. I don’t know whether the paperback copy is edited the same, but there are multiple spelling and capitalization errors in the tables and figures that are annoying (and there are a lot of tables and figures in the text).
Aside from the difficulties with the etextbook, the book leaves a lot to be desired. I’m utilizing this text for a graduate course, so I was forced to purchase it. It’s overly “wordy”, and could be condensed significantly. The material is a little challenging for folks new to the topic, and the authors aren’t very linear with their explanations. They provide a little information on a lot of topics, which leaves you having to Google better explanations. Then you find out in later chapters that they do cover the topic in more depth. Sometime they’ll tell you they’ll cover it later in the text, but much of the time they don’t. My instructor is teaching the course by jumping around the chapters, because the way the book is set up doesn’t lend itself to a linear approach through chapters. The book covers important topics, but it needs to be rewritten/organized to limit redundant explanations or wordiness, and to make the arrangement of the material more linear.