Database design for mere mortals a hands-on guide to relational database design Michael J. Hernandez

Enhanced descriptions from Syndetics:

Database design expert Michael J. Hernandez introduces the core concepts of design theory and method without the technical jargon. Database Design for Mere Mortals will provide any developer with a common-sense design methodology for developing databases that work.

Table of contents provided by Syndetics

• Foreword
• Preface and Acknowledgments
• I Relational Database Design
• 1 What Is a Relational Database?
• Types of Databases
• Early Database Models
• The Hierarchical Database Model
• The Network Database Model
• The Relational Database Model: A Brief History
• Relational Database Management Systems
• 2 Design Objectives
• Why Should You Be Concerned with Database Design?
• The Importance of Theory
• The Advantage of Learning Good Design Methodology
• The Importance of Understanding Database Design
• Objectives of Good Design
• Advantages of Good Design
• Database Design Methods
• Traditional Design Methods
• The Design Method Presented in This Book
• 3 Terminology
• Why This Terminology Is Important
• Value-related Terms
• Data
• Information
• Null
• Structure-related Terms
• Table
• Field
• Record
• View
• Keys
• Index
• Relationship-related Terms
• Relationships
• Types of Relationships
• Types of Participation
• Degree of Participation
• Integrity-related Terms
• Field Specification
• Data Integrity
• II The Design Process
• 4 Conceptual Overview
• The Importance of Completing the Design Process
• Defining a Mission Statement and Mission Objectives
• Analyzing the Current Database
• Creating the Data Structures
• Determining and Establishing Table Relationships
• Determining and Defining Business Rules
• Determining and Establishing Views
• Reviewing Data Integrity
• 5 Starting the Process
• Conducting Interviews
• 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
• 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
• Conducting User Interviews
• Reviewing Data Type and Usage
• Reviewing the Samples
• Reviewing Information Requirements
• Conducting Management Interviews
• 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
• 7 Establishing Table Structures
• Defining the Preliminary Table List
• Determining 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 Fi

Author notes provided by Syndetics

Michael J. Hernandez is a program manager for the Visual Studio .NET group at Microsoft, and is a veteran relational database developer with more than fourteen years of experience. He has been a premiere instructor with training organizations such as AppDev Training Co., Focal Point, Inc., and Deep Training, and was one of the first two hundred Microsoft-authorized .NET instructors. He speaks regularly at conferences.