Practical and easy to understand, DATABASE SYSTEMS: DESIGN, IMPLEMENTATION, AND MANAGEMENT, Tenth Edition, gives readers a solid foundation in database design and implementation. Filled with visual aids such as diagrams, illustrations, and tables, this market-leading book provides in-depth coverage of database design, demonstrating that the key to successful database implementation is in proper design of databases to fit within a larger strategic view of the data environment. Renowned for its clear, straightforward writing style, the tenth edition has been thoroughly updated to include hot topics such as green computing/sustainability for modern data centers, the role of redundant relationships, and examples of web-database connectivity and code security. In addition, new review questions, problem sets, and cases have been added throughout the book so that readers have multiple opportunities to test their understanding and develop real and useful design skills.
- I was required to buy this book for an introductory class to databases. My classes were entirely online, and the textbook was generally the only source of information given (ex, no lectures or instructor’s notes). I have no experience with databases at all, and was looking forward to learning about them.
This book is broken into very logical parts, and has a nice amount of “chunking” of information, with call-outs and plenty of diagrams. Props to the graphic designer. It covers a lot of material and tries to give as solid base of understanding for future database developers. It also includes a glossary in the back.
The text in the book left something to be desired. New terms would be defined using other new terms, forcing the reader to figure out 2 new terms at once. The book also would start to explain a concept, and then say that it was going to explain the concept further in later chapters over and over. I think the writers are very knowledgeable about what they are talking about, but would have done well to have a great technical writer help them convey that knowledge. Personally, I had to reread sections over and over trying to figure out exactly what the author meant. Eventually, I ended up going and looking up terms on Wikipedia to get a second explanation.
Overall, I think this book might be good if you have lectures or other resources in a class to help you understand databases. But on its own, this book has trouble getting all of its messages across clearly.
- I like the Kindle book, the price is less than the paper book. You can get the three first chapter for free and buy the whole later. If you buy the entire book it will keep your notes and highlights on the free chapters. I downloaded the free Kindle app on my windows and I can read it from there. I need to be online to read the book. I also bought the Kindle Fire HDX 7″ with 4G and WiFi from Amazon but have not used it yet . I don’t know if I need to be connected to WiFi to read the book from my Kindle Fire. I can use the 4G any ways,
The only problem I faced was I bought the Kindle Paper White first and this book doesn’t work on that type of Kindle tablets. I bought that from Amazon too along with the case and when I discovered the book does not go on it I returned the Paper White and case and seller refunded me really fast and free return. Also the Kindle free app installs on Android but you can’t read this book on android even if you install the app. Overall I like digital books better than paper books. Also as appose to other sellers when you buy Kindle book you will have it forever. Some other non Kindle and non Amazon version expire after a while and you lose the book.
- There is a LOT of information in this book. Some concepts are pounded into your head over and over and over again. You will spend several pages each on some very basic subjects. Prior reviews are correct about the multiple mentions of NoSQL sans good information about it. I don’t feel you’ll come away with a real tangible idea of what NoSQL really is. Early chapters focus heavily on diagramming (i.e. Entity Relationship Diagrams, UML Diagrams, etc.). This isn’t necessarily a bad thing, but the homework problems are hell when you’re assigned several of the problems in those chapters, especially when you didn’t yet download good diagramming tools (like yEd, Visio, or Microsoft Access).
Overall, you’ll learn a lot, but you’ll be exhausted by many of the chapters. A few chapters are around 50 pages and take at least two hours each to read. It’s not an easy read, and it helps if you already have a basic understanding of databases and what they do.
- The only upside is that subject material is easy to find through the search option. That being said, why are we still teaching professionals to begin with an inadequate database design, and then perfect it? If you have absolutely no idea how to construct a database and have never worked with one, you’ll probably like this book. For those with experience, there’s too much mundacity and aggravatingly simple examples. There is little in terms of security, which is arguably the most important aspect of building and running a database. The phrase “need to know” is everywhere in IT security, but you won’t find it in here. Instead, you’ll get a long-winded explanation of who needs what information, without ever learning how to secure your data.
- I had to buy this for a class which was based on this book. I’m almost not even sure where to start but I’ll start with the writing quality. Chapter 1, for example, starts out with a laborious discussion on the pros and cons of file-based systems vs. DBMS’s. One of the cons listed was that file-based systems require programmers while apparently forgetting that they were about to spend the rest of the book introducing the reader to SQL. This discussion might have been relevant 10-15 years ago but should’ve been dropped several editions ago.
Speaking of relevancy, the authors do make mention of NoSQL in the first chapter but then proceed to ignore it. You won’t find any discussions in this book about MongoDB or Cassandra and I’m not sure I ever saw MySQL mentioned either (so don’t look for a discussion on sharding). The authors are under the mistaken impression that DAO and RDO are viable even though Microsoft doesn’t. One can also not help but to get the distinct impression that they feel AS400’s are lurking everywhere and tend to compare everything to mainframes as a basis for discussion. The book does tackle data warehousing but you could probably learn the same lightweight material from a ‘Dummies’ book.
Unless you are forced to buy this book by the dinosaurs (or MBAs) running your computer science department you should consider avoiding this terrible book at all costs. I doubt that it would even be sold, much less be able to demand the price it does, if it wasn’t used as a textbook by out-of-touch academics.