Database Processing: Fundamentals, Design, and Implementation

Rating:
Summary: Avoid -do NOT use book as reference do NOT use in a class!
Review: I can see where this book would get a bad review; this is NOT a step by step book, but a real technical manual that explains DB model specifications (why they exist, how they work) with real database application development jargon. Not an easy read.

However his writing (English technical merit-very concise-to the point- language) and technical (database) expertise deserve David a 5 star rating.

Beware that this is not a weekend do it yourself build a database book, this would do as a text book for a university (in fact that is why I got it (berkeley university).

Rating:
Summary: Miserable Book
Review: I have to agree with the negative reviews so far. This book is a nightmare! I'm currently using this book for class.
The author contradicts himself not only from chapter to chapter but within individual paragraphs.
He spends entirely too much time on simple ideas and breezes through complex ones.
I find myself reading through paragraphs thinking, "Oh, he's still talking about that? Why is he still taking about that?"
Then the next paragraph, "What the hell is he talking about!?"
His sentences are wordy and complicated. He has forgotten the basic structure of the English sentence. That being: Stick to one subject per each, please. Throughout these verbose outbursts, he combines terms that are so similar they cause confusion. As an example:

"The physical description of a semantic object domain is just a reference to the semantic object description."

This gem of a sentence is halfway through Chapter Four. However, since this book is so poorly thought out and written, I still don't know what any of those terms mean or refer to.
If I knew what he was talking about, I would rewrite that sentence. However, I don't. So I've given up reading and am now writing a scathing review. What does that tell you?
Thankfully, there are many figures scattered throughout the book to attempt to clarify what the author can't seem to. Unfortunately, none of the figures being refered to are ever on the same page. The student must read the sentence, flip the page, try to remember what the author was rambling about, flip back, ... you get the point.

All in all, this is the most miserable textbook I have ever read. And perhaps one of the most overpriced. At "this cost", not only do expect this book to basically read itself, I would expect it to teach me through osmosis while I sleep.

Rating:
Summary: Miserable Book
Review: In response to some negative reviews, I think some are missing the point of why this book was written. This book's goal is not to teach you how to totally design and program a database from scratch. Its purpose is to familiarize readers with the various methods of designing and interacting with databases. The coverage of SQL is well done. Yes, there is more to it than what the book covers, but most of those details vary from DBMS to DBMS. Also, the ER diagram is covered well, although I would have appreciated a few more problems and examples that give the student practice in constructing a diagram from scratch. The much-maligned SOM was for me a good alternative perspective. Maybe it isn't used as much in industry, so what? It still helps the introductory student grasp the underlying concepts and think outside of the box. The later chapters are not extensive in their coverage of xml, asp, and the like but they don't have to be. Remember, this is NOT a book about any specific language. Professors have the freedom to delve into areas that they think are more important in more detail. It is a fine companion to professor lectures.

Rating:
Summary: Does this guy work for Microsoft?
Review: The author of this book seems to think the sun rises and set in Redmond, even contending that Microsoft is solely responsible for the success of ODBC. Yes 90% of the world's desktops have some version of MS Windows, but databases run on servers, not desktops. The complete neglect of non Microsoft products make this book incomplete at best, and present a very skewed view of the database world.

Rating:
Summary: Author Knows, The rest of us guess
Review: This book in its 8th edition still lacks clearity. I have a copy of the 7th edition also.

Whats wrong with this book:
1. Chapters are too wordy, examples fail to fully clearify what the author is trying to convey.

2. End of chapter questions have no solutions to review questions/problems to verify readers understanding of material.
Companion web site is weak also.
Author offers no real RE-Enforcement of topic.

3. Seems to rely on instructors to clear up text material.
Which in my opinion is a very bad mistake.

4. I had to search out other resources for re-enforcement and claification of material.

5. The author writes a whole appendix B section on a software product that covers designing databases(that I will never use). I think if the author would have taken the time to do that for chapters 3 and 4. One read through would have been enough.

Bottom line if you have to read a chapter more than twice to understand what the author is trying to convey. Then its not worth reading and a waste of time. Technology curve is at a 6 month change over, you no longer have 2 years to learn a subject.

Rating:
Summary: Author Knows, The rest of us guess
Review: This book is an excellent tool for young aspiring DBA's and System Analysts. Kroenke is long reknowned for his extensive database knowledge and techniques - and rightly so.

I reccommend this book to anyone wanting an analytical approach to designing a database. The semantic object model is a masterpiece. Obey it. Use it. It works.

Don't dis' Kroenke because he utilizes Microsoft in the book. I hate Microsoft as much as anyone involved in the IT field. Kroenke only uses Microsoft tools as a way to explain and provide examples of the text.

Rating:
Summary: Database Processing: Fundamentals, Design and Implementation
Review: This has got to be the worst book that I have ever read. The author tends to confuse you. I considered myself to be very knowledgable when it comes to databases however, after reading this book I'm more confused than ever. I found myself reading some of the chapters two-three times just to try and understand what the author was attempting to say. It is definitely not a book for beginners.

Rating:
Summary: A Very Good Database Design Textbook
Review: Very Good! It is a relational database design textbook. The SQL Server7.0 CD included is a great deal. It goes into E-R Modeling, Normalization and database implementation. Some weaknesses: occasionally the layout may throw out the reader's attention. For example, it is a lot better to discuss about a particular method of design followed by its implementation. The book attempts to first discuss all design methods, then implementation methods, causing some confusion. It is clear that the author would like to give a kick to Semantic Object Modeling (SOM), but it is a hard sale. E-R Modeling is far easier to understand and SOM adds little. In chapter 3 (E-R Modeling), they should ad an advise given to us in class; if the entity appears to be plural, you might need to break it into several entities. This will save a lot of time to students, later, when performing Normalization. The discussion about synthesis of relations (chapter 5 - Normalization) is GREAT! It takes away the "intuition" out of DK/NF. In fact, this chapter should be revised to further stress this concept and relate it to DK/NF. Also, DK/NF should be further explained (right now it is very hard to read and grasp, "intuition" can be taken out by using synthesis) and be central. All other "Normal Forms" need not be stressed, but present it as part of the history of how modification anomalies were initially handled. The reader of this review should still understand only one thing. The book is VERY GOOD. Only because I learned so much, I am now brave enough to suggest the author to revise it.