<< 1 >>
Rating: 
Summary: Best Introduction to Database Design Ever Written
Review: Everyone who works with databases should read this book. There are numerous How-To books for implementing databases with various products, but Mere Mortals is one of a kind. Most database problems are caused by poor design. If the data model is clear, developing is easy. Michael walks through the complete design process with clear language and valuable advice. Both novices and "experts" can benefit from studying this book. I used this book successfully in a beginning database development class, and I highly recommend it as a companion or prerequisite to any How-To book for Microsoft Access, SQL Server, Oracle, FoxPro, Sybase, or other DBMS.
Rating:
Summary: Exceptional and Easy to Understand
Review: I am a business (systems) analyst by profession and I highly recommend this book. Every IT business analyst should own this book and keep it close when defining technical requirements. The author is clear and concise and provides easy-to-understand definitions of relational database terms and how each object/element contributes to sound database design and, ultimately, data integrity.I read one of the other reviews before writing mine that mentioned that this book may be too simplistic for 'immortals' in the database design world. From what I've experienced in over 15 years in the industry, poor data quality continues to show its ugly head over and over. Maybe if some of those 'immortals' out there would revisit the basics of good database design, more data warehouses would succeed and projects would not overrun due to ever-present bad data! This is an excellent resource to review over and over again - I say, don't hesitate to buy this. You won't be disappointed (unless, of course, you're immortal!).
Rating:
Summary: NOT FOR EVERYONE (what else is new?)
Review: I have to temper my enthusiasm for this book with the perspective gained by reading the negative comments of those who seem to be, by and large, professional database developers, programming experts, and teachers. First, I just gotta say: "no offense, but geez, what a bunch of snotty know-it-alls!" Now that I have that off my chest, this book was manna from heaven for me! I am a newbie, I'm using Access, I'm trying to create a system for my workplace (without knowing what I'm doing, mind you!), and I learn best through a logical approach, reinforcement, and repitition. I actually enjoyed the experience of skipping some paragraphs thinking, "yeah, yeah, you said that already, I GOT it!" But I think even having that experience helps me learn by shoring up the information deposit in my head. If you're in my situation, and you like starting at the beginning and getting a solid foundation, AND if you're not a big whoopdie doo database mogul, you will love this book! BTW, this is not a book about Access or any particular brand of database software, but a book about FUNDAMENTALS of database design that is probably most appropriate for people who don't intend to make their living designing databases. I'd bet that's a lot of people.
Rating:
Summary: a turning point in my career
Review: If a computer book can be life-changing, this one would be. I had been working with databases for some time, but had no formal training. Often, I didn't understand the terms flying around, although I understood the concepts. This book defined all those database terms from normalization to join tables. It revolutionized the way I design databases. I particularly liked the focus on designing on paper first, because this provides a great requirements document and the basis for a user manual! Hernandez teaches you how to talk to the stakeholders and determine what the database needs to represent. He has a method for transforming a user interview into table and field names. The book is well-laid out with lots of examples, a typeset that's easy on the eyes, and extremely clear prose. I can't imagine where I would be today if I hadn't bought this book a year ago. My employers paid much less for this book than any class I have taken, and yet this has had the largest impact on the way I develop. Database applications I created after reading the book have gotten lots of good feedback from users.
Rating: 
Summary: First Edition (Please read the full review)
Review: Intro
"There is no one book that is best for every person. There couldn't be one. People are too different in the way they learn, in what they already know, in what they need, in what they want, and in what kind of effort they are willing to make." Bjarne Stroustrup (The creator of the C++ programming language.)
I always try to remember this whenever I have to judge a writing effort.
Whom is this book for?
This book is for a beginner database developer who wants a simple process to follow and some light intro to the fundamentals of database design.
What does this Book offer?
The main aim of the book is to offer a database development process that would help a novice get the basics of database development through light weight process the writer follows and I insist on the word light weight since the writer aims at abstracting some hard concepts in simple ways. Thought the process tips are given on how to conduct an interview, how to name tables, how to search for fields, light weight normalization.
What I liked?
This book is well written, simple and an easy read. The best of the book seems to be at the end.
What I didn't?
If you didn't, go read the Stroustrup quote I wrote in order not to miss understand me, the book seems to be aimed at shallow people :) never the less its good, the writer seems to think that he is the only good database developer and that he is always right
Conclusion
The book is not so deep but yes you may be able to design your own database system.
Rating:
Summary: A Must-Have For Beginners To Database Design
Review: Outstanding - Easy to read - Well written - Great book These are some of the comments from my students. I have been using this book for nearly a year now to teach an Access/Database Design class and my students love this book. Mr. Hernandez makes what could be a very complicated subject EASY to understand for students new to database design. It does belabor the user/management interviews. But here the author is emphasizing the fact that you are creating the database for users and management. Their input to the design is of paramount importance to its success and to help minimize future revisions to the design and RDBMS. If you're new to database design, or your concept of a database is one huge spreadsheet, BUY AND READ THIS BOOK and you'll be well on your way to building better databases.
Rating: 
Summary: there are better books out there
Review: This book is adequate but not great as an introduction to designing databases. I agree with other reviewers that it's quite repetitive and goes to extremes on details like field specifications. I suppose if you know nothing about DB design this book is OK - but you'll need other books and lots of practice designing your own databases if you truly want to become proficient. A much better general intro book to databases and simple design is 'Inside Relational Databases' by Whitehorn & Marklyn. Novices should look at 'Absolute Beginner's Guide to Databases' by John V. Petersen first. Once you've mastered those 2 books then get the best available book on DB design/modeling: 'Case*Method: Entity Relationship Modelling' by Richard Barker. It's excellent. Two other options for university level/advanced modeling: 'Database Modeling & Design' by Toby J. Teorey and 'Data Modeling Essentials: Analysis, Design, and Innovation' by Graeme C. Simsion
<< 1 >>
| 
