Database Design for Mere Mortals A Hands-On Guide to Relational Database Design

Database Design for Mere Mortals Cover Art

Author: Michael J. Hernandez
Publisher: Addison Wesley Developers Press
Year: 1997
Length: 440 pages
Format: Soft Cover
ISBN: 0201694719

Amazon Description
Relational databases are powerful tools for organizing data, but learning to use them effectively can be painful. Relational Database Design for Mere Mortals explains the concepts of relational-database design in an easy-to-digest fashion that covers both the theoretical underpinnings and their practical implications. Hernandez covers all the basics--table and field structure, keys, relationships, business rules, and more--but always keeps his feet on the ground with advice for real-world implementations and a particularly strong section on analyzing your current database infrastructure.

Commentary/Review

If I harbor any favorites of my technical books, then " Design for Mere Mortals" and "SQL Queries for Mere Mortals" both written by Michael J. Hernandez would qualify. Hernandez, owner of Seattle's DataTex Consulting Group, uses his 14 plus years in database design to create a book that is useful for novice and professionals alike.

You can tell that Michael has expertise in the training arena. Design for Mere Mortals is set-up like learning a skill or an approach. He introduces the basic theories and backgrounds, objectives and terminology, then transitions you to thought processes and design application. A good foundation for everyone.

The author, and I agree, recommends that you first read the book from beginning to end. For most technical books, I wouldn't even try. Even with my degree of technical knowledge they are far more suitable for selecting the chapter or pages closest to what you need, and doing focused spurts of learning. But Hernandez is actually a good technical writer. His grasp of the complex concepts is strong and firm enough that he can readily break them down into easy-to-understand parts for users.

I have a winding background in technology. Despite the dual study of Administration of Justice and Chemical Engineering in college, my introduction to "all things tech" came gradually through the pursuit of other interests. Since, I was fourteen, I had always worked with nonprofit organization, and had a keen interest in their organization, development and administration. This interest kept me actively involved in grassroots organizing while in college.

Oddly, or not so oddly, grassroots organizing got me involved in a number of computer related technology areas. I started with graphic design and desktop publishing. Rapidly growing my skills and expertise into above par marketing skills. Marketing skills lead to contact and communication skills, which inevitably lead me down the path to database design.

My first "ah-hah" moment with database design was when reading the user manual that was shipped with FileMaker Pro 2.0. In that day and age, FileMaker was still part of Claris,and Claris was an Apple subsidiary. But, most user manuals are worthless; but since I knew less than zero about FileMaker, and very little about databases of any type, I opened it. Imagine my surprise at a good foundation for understanding the basic concepts of how data relates and different methods and ideologies for breaking it down and joining it together.

Years of reading books on data structuring, data modeling, data integrity, relational design theory, and more, never duplicated that initial, revealing, introduction into the basics of database design. Then came along "Database Design for Mere Mortals" by Hernandez. I was looking for a book that would give me better insight into data integrity and business rules.

I wanted a simplistic by deep reaching understanding of the two concepts so, I could determine how to maintain data integrity, while implementing business rules in a manner that didn't destroy natural human-computer interactions. Sounds complicated, but basically what I was tired of, was database interfaces (the part the user sees) that breaks information down to each manipulatable component. So an street address might become number, street, type, apartment, four distinct fields, instead of "123 Main Street, Ste 3" one specific address, at least in terms of how individuals interact with it.

I wanted a methodology to recombine data for the user experience, and have that same data divided into manipulatable parts for the machine. And to do that, I needed to rid myself of the complexity of data integrity and business rules, and just understand their simple core functionality. Hernandez created the "ah-hah" experience for me, and even expanded to other areas of the design process and design fundamentals. I became a better developer, more instinctive, and better able to comprehend client's needs; despite their ability to often obfuscate them.

I often go back to "Database Design..." when I feel like I'm complicating a concept for a client. The language and clarity allows me to focus, and restate definitions in ways that are easier to understand; and drives home the fundamentals.

I highly recommend that if you do any type of work on the regular basis with databases, get this book. If your just a novice office user or the designer/developer. Mere Mortals really is a common-sense approach to database design methodology that's readily accessible for your use.

Rating

Four Star Rating

Purchase Notice

Note: All books can mentioned in this section of the website can be purchased at Amazon.com. Proceeds from the Amazon.com Associate directly benefit Nonprofit Tech, a 501(c)(3) organization dedicating to providing technology services for nonprofit, educational, and public institutions; whom I work with. If that does not discourage you, then buy Database Design for Mere Mortals from Amazon.com

Other Details

Genre: Computers & Internet, Databases, Database Design, Relational Database Theory
Categories: technical
Viewed: 1648
Comments: 0
Permalink: http://www.wide-eyed.org/books/article/database_design_for_mere_mortals/

Comments

    Sorry, no comments right now; but you could be the first.

Name:

Emai (*)l:

Location:

URL:

Smileys

Remember my personal information

Notify me of follow-up comments?

 

Page rendered in 0.4676 seconds | 59 querie(s) executed | Update