Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design / Edition 2

Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design / Edition 2

by Michael J. Hernandez, Ken Getz
Pub. Date:
Select a Purchase Option (Revised with CD-ROM)
  • purchase options
    $14.22 $74.99 Save 81%
    • Free return shipping at the end of the rental period details
    • Textbook Rentals in 3 Easy Steps  details
    Note: Access code and/or supplemental material are not guaranteed to be included with textbook rental or used textbook.
  • purchase options
    $31.13 $74.99 Save 58% Current price is $31.13, Original price is $74.99. You Save 58%.
    Note: Access code and/or supplemental material are not guaranteed to be included with textbook rental or used textbook.
  • purchase options


Database Design for Mere Mortals: A Hands-On Guide to Relational Database Design / Edition 2

“This book takes the somewhat daunting process of database design and breaks it into completely manageable and understandable components. Mike’s approach whilst simple is completely professional, and I can recommend this book to any novice database designer.”

Sandra Barker, Lecturer, University of South Australia, Australia

“Databases are a critical infrastructure technology for information systems and today’s business. Mike Hernandez has written a literate explanation of database technology–a topic that is intricate and often obscure. If you design databases yourself, this book will educate you about pitfalls and show you what to do. If you purchase products that use a database, the book explains the technology so that you can understand what the vendor is doing and assess their products better.”

Michael Blaha, consultant and trainer, author of A Manager’s Guide to Database Technology

“If you told me that Mike Hernandez could improve on the first edition of Database Design for Mere Mortals I wouldn’t have believed you, but he did! The second edition is packed with more real-world examples, detailed explanations, and even includes database-design tools on the CD-ROM! This is a must-read for anyone who is even remotely interested in relational database design, from the individual who is called upon occasionally to create a useful tool at work, to the seasoned professional who wants to brush up on the fundamentals. Simply put, if you want to do it right, read this book!”

Matt Greer, Process Control Development, The Dow Chemical Company

“Mike’s approach to database design is totally common-sense based, yet he’s adhered to all the rules of good relational database design. I use Mike’s books in my starter database-design class, and I recommend his books to anyone who’s interested in learning how to design databases or how to write SQL queries.”

Michelle Poolet, President, MVDS, Inc.

“Slapping together sophisticated applications with poorly designed data will hurt you just as much now as when Mike wrote his first edition, perhaps even more. Whether you’re just getting started developing with data or are a seasoned pro; whether you've read Mike’s previous book or this is your first; whether you're happier letting someone else design your data or you love doing it yourself–this is the book for you. Mike’s ability to explain these concepts in a way that’s not only clear, but fun, continues to amaze me.”

–From the Foreword by Ken Getz, MCW Technologies, coauthor ASP.NET Developer's JumpStart

“The first edition of Mike Hernandez’s book Database Design for Mere Mortals was one of the few books that survived the cut when I moved my office to smaller quarters. The second edition expands and improves on the original in so many ways. It is not only a good, clear read, but contains a remarkable quantity of clear, concise thinking on a very complex subject. It’s a must for anyone interested in the subject of database design.”

Malcolm C. Rubel, Performance Dynamics Associates

“Mike’s excellent guide to relational database design deserves a second edition. His book is an essential tool for fledgling Microsoft Access and other desktop database developers, as well as for client/server pros. I recommend it highly to all my readers.”

Roger Jennings, author of Special Edition Using Access 2002

“There are no silver bullets! Database technology has advanced dramatically, the newest crop of database servers perform operations faster than anyone could have imagined six years ago, but none of these technological advances will help fix a bad database design, or capture data that you forgot to include! Database Design for Mere Mortals™, Second Edition, helps you design your database right in the first place!”

Matt Nunn, Product Manager, SQL Server, Microsoft Corporation

“When my brother started his professional career as a developer, I gave him Mike’s book to help him understand database concepts and make real-world application of database technology. When I need a refresher on the finer points of database design, this is the book I pick up. I do not think that there is a better testimony to the value of a book than that it gets used. For this reason I have wholeheartedly recommended to my peers and students that they utilize this book in their day-to-day development tasks.”

Chris Kunicki, Senior Consultant,

“Mike has always had an incredible knack for taking the most complex topics, breaking them down, and explaining them so that anyone can ‘get it.’ He has honed and polished his first very, very good edition and made it even better. If you're just starting out building database applications, this book is a must-read cover to cover. Expert designers will find Mike’s approach fresh and enlightening and a source of great material for training others.”

John Viescas, President, Viescas Consulting, Inc., author of Running Microsoft Access 2000 and coauthor of SQL Queries for Mere Mortals

“Whether you need to learn about relational database design in general, design a relational database, understand relational database terminology, or learn best practices for implementing a relational database, Database Design for Mere Mortals™, Second Edition, is an indispensable book that you’ll refer to often. With his many years of real-world experience designing relational databases, Michael shows you how to analyze and improve existing databases, implement keys, define table relationships and business rules, and create data views, resulting in data integrity, uniform access to data, and reduced data-entry errors.”

Paul Cornell, Site Editor, MSDN Office Developer Center

Sound database design can save hours of development time and ensure functionality and reliability. Database Design for Mere Mortals™, Second Edition, is a straightforward, platform-independent tutorial on the basic principles of relational database design. It provides a commonsense design methodology for developing databases that work.

Database design expert Michael J. Hernandez has expanded his best-selling first edition, maintaining its hands-on approach and accessibility while updating its coverage and including even more examples and illustrations.

This edition features a CD-ROM that includes diagrams of sample databases, as well as design guidelines, documentation forms, and examples of the database design process.

This book will give you the knowledge and tools you need to create efficient and effective relational databases.

Product Details

ISBN-13: 9780201752847
Publisher: Addison-Wesley
Publication date: 03/07/2003
Series: For Mere Mortals Series
Edition description: Revised with CD-ROM
Pages: 611
Product dimensions: 7.37(w) x 9.25(h) x 1.39(d)

Table of Contents



1. What Is a Relational Database.
Types of Databases.
Early Database Models.
The Hierarchical Database Model.
The Network Database Model.

The Relational Database Model.
Retrieving Data.
Advantages of a Relational Database.

Relational Database Management Systems.
Beyond the Relational Model.
What the Future Holds.
A Final Note.

Review Questions.

2. Design Objectives.
Why Should You Be Concerned with Database Design?
The Importance of Theory.
The Advantage of Learning A Good Design Methodology.
Objectives of Good Design.
Benefits of Good Design.
Database Design Methods.
Traditional Design Methods.
The Design Method Presented in This Book.

Review Questions.

3. Terminology.
Why This Terminology Is Important.
Value-related Terms.

Structure-related Terms.

Relationship-related Terms.
Types of Relationships.
Types of Participation.
Degree of Participation.

Integrity-related Terms.
Field Specification.
Data Integrity.

Review Questions.


4. Conceptual Overview.
The Importance of Completing the Design Process.
Define a Mission Statement and Mission Objectives.
Analyze the Current Database.
Create the Data Structures.
Determine and Establish Table Relationships.
Determine and Define Business Rules.
Determine and Define Views.
Review Data Integrity.
Review Questions.

5. Starting the Process.
Conducting Interviews.
Participant Guidelines.
Interviewer Guidelines.

The Case Study: Mike's Bikes.
Defining the Mission Statement.
The Well-written Mission Statement.
Composing a Mission Statement.
Case Study.

Defining the Mission Objectives.
Well-written Mission Objectives.
Composing Mission Objectives.
Case Study.

Review Questions.

6. Analyzing the Current Database.
Getting to Know the Current Database.
Paper-based Databases.
Legacy Databases.

Conducting the Analysis.
Looking at How Data Is Collected.
Looking at How Information Is Presented.
Conducting Interviews.
Basic Interview Techniques.
Before You Begin the Interview Process.

Interviewing Users.
Reviewing Data Type and Usage.
Reviewing the Samples.
Reviewing Information Requirements.

Interviewing Management.
Reviewing Current Information Requirements.
Reviewing Additional Information Requirements.
Reviewing Future Information Requirements.
Reviewing Overall Information Requirements.

Compiling a Complete List of Fields.
The Preliminary Field List.
The Calculated Field List.
Reviewing Both Lists with Users and Management.

Case Study.
Review Questions.

7. Establishing Table Structures.
Defining the Preliminary Table List.
Identifying Implied Subjects.
Using the List of Subjects.
Using the Mission Objectives.

Defining the Final Table List.
Refining the Table Names.
Indicating the Table Types.
Composing the Table Descriptions.

Associating Fields with Each Table.
Refining the Fields.
Improving the Field Names.
Using the Ideal Field to Resolve Anomalies.
Resolving Mulit-part Fields.
Resolving Multi-valued Fields.

Refining the Table Structures.
A Word about Redundant Data and Duplicate Fields.
Using the Ideal Table to Refine Table Structures.
Establishing Subset Tables.

Case Study.
Review Questions.

8. Keys.
Why Keys Are Important.
Establishing Keys for Each Table.
Candidate Keys.
Primary Keys.
Alternate Keys.
Table-Level Integrity.

Reviewing the Initial Table Structures.
Case Study.
Review Questions.

9. Field Specifications.
Why Field Specifications Are Important.
Field-Level Integrity.
Anatomy of a Field Specification.
General Elements.
Physical Elements.
Logical Elements.

Using Unique, Generic, and Replica Field Specifications.
Defining Field Specifications for Each Field in the Database.
Case Study.
Review Questions.

10. Table Relationships.
Types of Relationships.
One-to-One Relationships.
One-to-Many Relationships.
Many-to-Many Relationships.
Self-referencing Relationships.

Identifying Existing Relationships.
Establishing Each Relationship.
One-to-One and One-to-Many Relationships.
Many-to-Many Relationships.
Self-referencing Relationships.
Reviewing the Structure of Each Table.

Refining All Foreign Keys.
Elements of a Foreign Key.

Establishing Relationship Characteristics.
Defining a Deletion Rule for Each Relationship.
Identifying the Type of Participation for Each Table.
Identifying the Degree of Participation for Each Table.
Verifying Table Relationships with Users and Management.
A Final Note.

Relationship-Level Integrity.
Case Study.
Review Questions. Chapter 11: Business Rules.
What Are Business Rules?
Types of Business Rules.

Categories of Business Rules.
Field-specific Business Rules.
Relationship-specific Business Rules.

Defining and Establishing Business Rules.
Working with Users and Management.
Defining and Establishing Field-Specific Business Rules.
Defining and Establishing Relationship-Specific Business Rules.

Validation Tables.
What Are Validation Tables?
Using Validation Tables to Support Business Rules.

Reviewing the Business Rule Specification Sheets.
Case Study.
Review Questions.

What Are Views?
Anatomy of a View.
Data View.
Aggregate View.
Validation View.

Determining and Defining Views.
Working with Users and Management.
Defining Views.
Reviewing the Documentation for Each View.

Case Study.
Review Questions.

13. Reviewing Data Integrity.
Why You Should Review Data Integrity.
Reviewing and Refining Data Integrity.
At the Table Level.
At the Field Level.
At the Relationship Level.
At the Level of Business Rules.
At the Level of Views.

Assembling the Database Documentation.
Done at Last!
Case Study—Wrap up.


14. Bad Design—What Not To Do.
Flat-File Design.
Spreadsheet Design.
Dealing with the Spreadsheet View Mind-set.

Database Design Based on Database Software.
A Final Thought.

15. Bending or Breaking the Rules.
When May You Bend or Break the Rules?
Designing an Analytical Database.
Improving Processing Performance.

Documenting Your Actions.

In Closing.


Appendix A: Answers to Review Questions.
Appendix B: Diagram of the Database Design Process.
Appendix C: Design Guidelines.
Appendix D: Documentation Forms.
Appendix E: Database Design Diagram Symbols.
Appendix F: Sample Designs.
Appendix G: Recommended Reading.

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews