gogogo
Syndetics cover image
Image from Syndetics

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

By: Material type: TextTextPublication details: Upper Saddle River, NJ : Addison-Wesley, [2013], ©2013.Edition: Third editionDescription: xliii, 610 pages : illustrations ; 24 cmISBN:
  • 9780321884497 : PAP
  • 0321884493 : PAP
Subject(s): DDC classification:
  • 005.756 HER
Holdings
Item type Current library Call number Copy number Status Date due Barcode
Standard Loan Clonmel Library Main Collection 005.756 HER (Browse shelf(Opens below)) 0 Available 39002100621334
Standard Loan Thurles Library Main Collection 005.756 HER (Browse shelf(Opens below)) 1 Available 39002100654657

Enhanced descriptions from Syndetics:



The #1 Easy, Commonsense Guide to Database Design! Michael J. Hernandez's best-selling Database Design for Mere Mortals® has earned worldwide respect as the clearest, simplest way to learn relational database design. Now, he's made this hands-on, software-independent tutorial even easier, while ensuring that his design methodology is still relevant to the latest databases, applications, and best practices. Step by step, Database Design for Mere Mortals ® , Third Edition, shows you how to design databases that are soundly structured, reliable, and flexible, even in modern web applications. Hernandez guides you through everything from database planning to defining tables, fields, keys, table relationships, business rules, and views. You'll learn practical ways to improve data integrity, how to avoid common mistakes, and when to break the rules.

Coverage includes

Understanding database types, models, and design terminology

Discovering what good database design can do for you--and why bad design can make your life miserable

Setting objectives for your database, and transforming those objectives into real designs

Analyzing a current database so you can identify ways to improve it

Establishing table structures and relationships, assigning primary keys, setting field specifications, and setting up views

Ensuring the appropriate level of data integrity for each application

Identifying and establishing business rules


Whatever relational database systems you use, Hernandez will help you design databases that are robust and trustworthy. Never designed a database before? Settling for inadequate generic designs? Running existing databases that need improvement? Start here.

Table of contents provided by Syndetics

  • Foreword (p. xxi)
  • Preface (p. xxv)
  • Acknowledgments (p. xxvii)
  • Introduction (p. xxix)
  • Part I Relational Database Design (p. 1)
  • Chapter 1 The Relational Database (p. 3)
  • Topics Covered in This Chapter (p. 3)
  • Types of Databases (p. 4)
  • Early Database Models (p. 5)
  • The Hierarchical Database Model (p. 5)
  • The Network Database Model (p. 9)
  • The Relational Database Model (p. 12)
  • Retrieving Data (p. 15)
  • Advantages of a Relational Database (p. 16)
  • Relational Database Management Systems (p. 18)
  • Beyond the Relational Model (p. 19)
  • What the Future Holds (p. 21)
  • A Final Note (p. 22)
  • Summary (p. 22)
  • Review Questions (p. 24)
  • Chapter 2 Design Objectives (p. 25)
  • Topics Covered in This Chapter (p. 25)
  • Why Should You Be Concerned with Database Design? (p. 25)
  • The Importance of Theory (p. 27)
  • The Advantage of Learning a Good Design Methodology (p. 29)
  • Objectives of Good Design (p. 30)
  • Benefits of Good Design (p. 31)
  • Database Design Methods (p. 32)
  • Traditional Design Methods (p. 32)
  • The Design Method Presented in This Book (p. 34)
  • Normalization (p. 35)
  • Summary (p. 38)
  • Review Questions (p. 39)
  • Chapter 3 Terminology (p. 41)
  • Topics Covered in This Chapter (p. 41)
  • Why This Terminology Is Important (p. 41)
  • Value-Related Terms (p. 43)
  • Data (p. 43)
  • Information (p. 43)
  • Null (p. 45)
  • The Value of Nulls (p. 46)
  • The Problem with Nulls (p. 47)
  • Structure-Related Terms (p. 49)
  • Table (p. 49)
  • Field (p. 52)
  • Record (p. 53)
  • View (p. 54)
  • Keys (p. 56)
  • Index (p. 58)
  • Relationship-Related Terms (p. 59)
  • Relationships (p. 59)
  • Types of Relationships (p. 60)
  • Types of Participation (p. 65)
  • Degree of Participation (p. 66)
  • Integrity-Related Terms (p. 67)
  • Field Specification (p. 67)
  • Data Integrity (p. 68)
  • Summary (p. 69)
  • Review Questions (p. 70)
  • Part II The Design Process (p. 73)
  • Chapter 4 Conceptual Overview (p. 75)
  • Topics Covered in This Chapter (p. 75)
  • The Importance of Completing the Design Process (p. 76)
  • Defining a Mission Statement and Mission Objectives (p. 77)
  • Analyzing the Current Database (p. 78)
  • Creating the Data Structures (p. 80)
  • Determining and Establishing Table Relationships (p. 81)
  • Determining and Defining Business Rules (p. 81)
  • Determining and Defining Views (p. 83)
  • Reviewing Data Integrity (p. 83)
  • Summary (p. 84)
  • Review Questions (p. 86)
  • Chapter 5 Starting the Process (p. 89)
  • Topics Covered in This Chapter (p. 89)
  • Conducting Interviews (p. 89)
  • Participant Guidelines (p. 91)
  • Interviewer Guidelines (These Are for You) (p. 93)
  • The Case Study: Mike's Bikes (p. 98)
  • Defining the Mission Statement (p. 100)
  • The Well-Written Mission Statement (p. 100)
  • Composing a Mission Statement (p. 102)
  • Defining the Mission Objectives (p. 105)
  • Well-Written Mission Objectives (p. 106)
  • Composing Mission Objectives (p. 108)
  • Summary (p. 112)
  • Review Questions (p. 113)
  • Chapter 6 Analyzing the Current Database (p. 115)
  • Topics Covered in This Chapter (p. 115)
  • Getting to Know the Current Database (p. 115)
  • Paper-Based Databases (p. 118)
  • Legacy Databases (p. 119)
  • Conducting the Analysis (p. 121)
  • Looking at How Data Is Collected (p. 121)
  • Looking at How Information Is Presented (p. 125)
  • Conducting Interviews (p. 129)
  • Basic Interview Techniques (p. 130)
  • Before You Begin the Interview Process ... (p. 137)
  • Interviewing Users (p. 137)
  • Reviewing Data Type and Usage (p. 138)
  • Reviewing the Samples (p. 140)
  • Reviewing Information Requirements (p. 144)
  • Interviewing Management (p. 152)
  • Reviewing Current Information Requirements (p. 153)
  • Reviewing Additional Information Requirements (p. 154)
  • Reviewing Future Information Requirements (p. 155)
  • Reviewing Overall Information Requirements (p. 155)
  • Compiling a Complete List of Fields (p. 157)
  • The Preliminary Field List (p. 157)
  • The Calculated Field List (p. 164)
  • Reviewing Both Lists with Users and Management (p. 165)
  • Case Study (p. 166)
  • Summary (p. 171)
  • Review Questions (p. 172)
  • Chapter 7 Establishing Table Structures (p. 175)
  • Topics Covered in This Chapter (p. 175)
  • Defining the Preliminary Table List (p. 176)
  • Identifying Implied Subjects (p. 176)
  • Using the List of Subjects (p. 178)
  • Using the Mission Objectives (p. 182)
  • Defining the Final Table List (p. 184)
  • Refining the Table Names (p. 186)
  • Indicating the Table Types (p. 192)
  • Composing the Table Descriptions (p. 192)
  • Associating Fields with Each Table (p. 199)
  • Refining the Fields (p. 202)
  • Improving the Field Names (p. 202)
  • Using an Ideal Field to Resolve Anomalies (p. 206)
  • Resolving Multipart Fields (p. 210)
  • Resolving Multivalued Fields (p. 212)
  • Refining the Table Structures (p. 219)
  • A Word about Redundant Data and Duplicate Fields (p. 219)
  • Using an Ideal Table to Refine Table Structures (p. 220)
  • Establishing Subset Tables (p. 228)
  • Case Study (p. 233)
  • Summary (p. 240)
  • Review Questions (p. 242)
  • Chapter 8 Keys (p. 243)
  • Topics Covered in This Chapter (p. 243)
  • Why Keys Are Important (p. 244)
  • Establishing Keys for Each Table (p. 244)
  • Candidate Keys (p. 245)
  • Primary Keys (p. 253)
  • Alternate Keys (p. 260)
  • Non-keys (p. 261)
  • Table-Level Integrity (p. 261)
  • Reviewing the Initial Table Structures (p. 261)
  • Case Study (p. 263)
  • Summary (p. 269)
  • Review Questions (p. 270)
  • Chapter 9 Field Specifications (p. 273)
  • Topics Covered in This Chapter (p. 273)
  • Why Field Specifications Are Important (p. 274)
  • Field-Level Integrity (p. 275)
  • Anatomy of a Field Specification (p. 277)
  • General Elements (p. 277)
  • Physical Elements (p. 285)
  • Logical Elements (p. 292)
  • Using Unique, Generic, and Replica Field Specifications (p. 300)
  • Defining Field Specifications for Each Field in the Database (p. 306)
  • Case Study (p. 308)
  • Summary (p. 310)
  • Review Questions (p. 311)
  • Chapter 10 Table Relationships (p. 313)
  • Topics Covered in This Chapter (p. 313)
  • Why Relationships Are Important (p. 314)
  • Types of Relationships (p. 315)
  • One-to-One Relationships (p. 316)
  • One-to-Many Relationships (p. 319)
  • Many-to-Many Relationships (p. 321)
  • Self-Referencing Relationships (p. 329)
  • Identifying Existing Relationships (p. 333)
  • Establishing Each Relationship (p. 344)
  • One-to-One and One-to-Many Relationships (p. 345)
  • The Many-to-Many Relationship (p. 352)
  • Self-Referencing Relationships (p. 358)
  • Reviewing the Structure of Each Table (p. 364)
  • Refining All Foreign Keys (p. 365)
  • Elements of a Foreign Key (p. 365)
  • Establishing Relationship Characteristics (p. 372)
  • Defining a Deletion Rule for Each Relationship (p. 372)
  • Identifying the Type of Participation for Each Table (p. 377)
  • Identifying the Degree of Participation for Each Table (p. 380)
  • Verifying Table Relationships with Users and Management (p. 383)
  • A Final Note (p. 383)
  • Relationship-Level Integrity (p. 384)
  • Case Study (p. 384)
  • Summary (p. 389)
  • Review Questions (p. 391)
  • Chapter 11 Business Rules (p. 393)
  • Topics Covered in This Chapter (p. 393)
  • What Are Business Rules? (p. 393)
  • Types of Business Rules (p. 397)
  • Categories of Business Rules (p. 399)
  • Field-Specific Business Rules (p. 399)
  • Relationship-Specific Business Rules (p. 401)
  • Defining and Establishing Business Rules (p. 402)
  • Working with Users and Management (p. 402)
  • Defining and Establishing Field-Specific Business Rules (p. 403)
  • Defining and Establishing Relationship-Specific Business Rules (p. 412)
  • Validation Tables (p. 417)
  • What Are Validation Tables? (p. 419)
  • Using Validation Tables to Support Business Rules (p. 420)
  • Reviewing the Business Rule Specifications Sheets (p. 425)
  • Case Study (p. 426)
  • Summary (p. 431)
  • Review Questions (p. 434)
  • Chapter 12 Views (p. 435)
  • Topics Covered in This Chapter (p. 435)
  • What Are Views? (p. 435)
  • Anatomy of a View (p. 437)
  • Data View (p. 437)
  • Aggregate View (p. 442)
  • Validation View (p. 446)
  • Determining and Defining Views (p. 448)
  • Working with Users and Management (p. 449)
  • Defining Views (p. 450)
  • Reviewing the Documentation for Each View (p. 458)
  • Case Study (p. 460)
  • Summary (p. 465)
  • Review Questions (p. 466)
  • Chapter 13 Reviewing Data Integrity (p. 469)
  • Topics Covered in This Chapter (p. 469)
  • Why You Should Review Data Integrity (p. 470)
  • Reviewing and Refining Data Integrity (p. 470)
  • Table-Level Integrity (p. 471)
  • Field-Level Integrity (p. 471)
  • Relationship-Level Integrity (p. 472)
  • Business Rules (p. 472)
  • Views (p. 473)
  • Assembling the Database Documentation (p. 473)
  • Done at Last! (p. 475)
  • Case Study-Wrap-Up (p. 475)
  • Summary (p. 476)
  • Part III Other Database Design Issues (p. 477)
  • Chapter 14 Bad Design-What Not to Do (p. 479)
  • Topics Covered in This Chapter (p. 479)
  • Flat-File Design (p. 480)
  • Spreadsheet Design (p. 481)
  • Dealing with the Spreadsheet View Mind-set (p. 483)
  • Database Design Based on the Database Software (p. 485)
  • A Final Thought (p. 486)
  • Summary (p. 487)
  • Chapter 15 Bending or Breaking the Rules (p. 489)
  • Topics Covered in This Chapter (p. 489)
  • When May You Bend or Break the Rules? (p. 489)
  • Designing an Analytical Database (p. 489)
  • Improving Processing Performance (p. 490)
  • Documenting Your Actions (p. 493)
  • Summary (p. 495)
  • In Closing (p. 497)
  • Part IV Appendixes (p. 499)
  • Appendix A Answers to Review Questions (p. 501)
  • Chapter 1 (p. 501)
  • Chapter 2 (p. 502)
  • Chapter 3 (p. 504)
  • Chapter 4 (p. 505)
  • Chapter 5 (p. 506)
  • Chapter 6 (p. 508)
  • Chapter 7 (p. 510)
  • Chapter 8 (p. 513)
  • Chapter 9 (p. 516)
  • Chapter 10 (p. 518)
  • Chapter 11 (p. 520)
  • Chapter 12 (p. 521)
  • Appendix B Diagram of the Database Design Process (p. 525)
  • Appendix C Design Guidelines (p. 543)
  • Defining and Establishing Field-Specific Business Rules (p. 543)
  • Defining and Establishing Relationship-Specific Business Rules (p. 543)
  • Elements of a Candidate Key (p. 544)
  • Elements of a Foreign Key (p. 544)
  • Elements of a Primary Key (p. 545)
  • Rules for Establishing a Primary Key (p. 545)
  • Elements of the Ideal Field (p. 545)
  • Elements of the Ideal Table (p. 546)
  • Field-Level Integrity (p. 546)
  • Guidelines for Composing a Field Description (p. 547)
  • Guidelines for Composing a Table Description (p. 547)
  • Guidelines for Creating Field Names (p. 548)
  • Guidelines for Creating Table Names (p. 548)
  • Identifying Relationships (p. 549)
  • Identifying View Requirements (p. 549)
  • Interview Guidelines (p. 550)
  • Participant Guidelines (p. 550)
  • Interviewer Guidelines (p. 550)
  • Mission Statements (p. 551)
  • Mission Objectives (p. 551)
  • Relationship-Level Integrity (p. 551)
  • Resolving a Multivalued Field (p. 552)
  • Table-Level Integrity (p. 552)
  • Appendix D Documentation Forms (p. 553)
  • Appendix E Database Design Diagram Symbols (p. 557)
  • Appendix F Sample Designs (p. 559)
  • Appendix G On Normalization (p. 567)
  • Please Note ... (p. 568)
  • A Brief Recap (p. 569)
  • How Normalization Is Integrated into My Design Methodology (p. 572)
  • Logical Design versus Physical Design and Implementation (p. 575)
  • Appendix H Recommended Reading (p. 577)
  • Glossary (p. 579)
  • References (p. 595)
  • Index (p. 597)

Author notes provided by Syndetics

Michael J. Hernandez, a relational database developer with more than twenty years of experience, was a program manager and product manager for Microsoft's Visual Studio group. He has been a premier instructor with organizations such as AppDev Training Co., Focal Point, Inc., and Deep Training, and was a top-rated speaker at technical conferences across the United States, Europe, and South America. With John L. Viescas, he coauthored SQL Queries for Mere Mortals®, Second Edition (Addison-Wesley, 2008).

Powered by Koha