book

Database Design for Mere Mortals

by Michael J. Hernandez

December 1996

Intermediate to advanced

480 pages

8h 46m

English

Addison-Wesley Professional

Read now

Unlock full access

Dedication
About the AuthorForewordPreface and AcknowledgmentsIntroductionWho Should Read This BookThe Purpose of This BookHow to Read This BookHow This Book Is OrganizedPart One: Relational Database DesignPart Two: The Design ProcessPart Three: Other Database Design IssuesIMPORTANT: READ THIS SECTION!A Word About the Examples and Techniques in This BookA New Approach to Learning
Types of DatabasesEarly Database ModelsThe Hierarchical Database ModelThe Network Database ModelThe Relational Database Model: A Brief HistoryRelational Database Management SystemsSummary
Why Should You Be Concerned with Database Design?The Importance of TheoryThe Advantage of Learning Good Design MethodologyThe Importance of Understanding Database DesignObjectives of Good DesignAdvantages of Good DesignDatabase Design MethodsTraditional Design MethodsThe Design Method Presented in This BookSummary
Why This Terminology Is ImportantValue-related TermsDataInformationNullStructure-related TermsTableFieldRecordViewKeysIndexRelationship-related TermsRelationshipsTypes of RelationshipsOne-to-One RelationshipsOne-to-Many RelationshipsMany-to-Many RelationshipsTypes of ParticipationDegree of ParticipationIntegrity-related TermsField SpecificationData IntegritySummary
The Importance of Completing the Design ProcessDefining a Mission Statement and Mission ObjectivesAnalyzing the Current DatabaseCreating the Data StructuresDetermining and Establishing Table RelationshipsDetermining and Defining Business RulesDetermining and Establishing ViewsReviewing Data IntegritySummary
Conducting InterviewsTHE CASE STUDY: MIKES'S BIKESDefining the Mission StatementThe Well-Written Mission StatementComposing a Mission StatementCASE STUDYDefining The Mission ObjectivesWell-Written Mission ObjectivesComposing Mission ObjectivesCASE STUDYSummary
Getting to Know the Current DatabasePaper-based DatabasesLegacy DatabasesConducting the AnalysisLooking at How Data Is CollectedLooking at How Information Is PresentedConducting InterviewsConducting User InterviewsReviewing Data Type and UsageReviewing the SamplesReviewing Information RequirementsCurrent Information RequirementsAdditional Information RequirementsFuture Information RequirementsConducting Management InterviewsReviewing Current Information RequirementsReviewing Additional Information RequirementsReviewing Future Information RequirementsReviewing Overall Information RequirementsCompiling a Complete List of FieldsThe Preliminary Field ListThe Calculated Field ListReviewing Both Lists with Users and ManagementCASE STUDYSummary

Defining the Preliminary Table ListDetermining Implied SubjectsUsing the List of SubjectsUsing the Mission ObjectivesDefine the Final Table ListRefining the Table NamesGuidelines for Creating a Table NamesIndicating the Table TypesComposing the Table DescriptionsGuidelines for Composing a Table DescriptionInterviewing Users and ManagementAssociating Fields with Each TableRefining the FieldsImproving the Field NamesGuidelines for Creating Field NamesUsing the Ideal Field to Resolve AnomaliesElements of the Ideal FieldResolving Multipart FieldsResolving Multivalued FieldsRefining the Table StructuresA Word about Redundant Data and Duplicate FieldsUsing the Ideal Table to Refine Table StructuresElements of the Ideal TableResolving Unnecessary Duplicate FieldsEstablishing Subset TablesRefine Previously Unidentified Subset TablesCASE STUDYSummary
Why Keys Are ImportantEstablishing Keys for Each TableCandidate KeysElements of a Candidate KeyArtificial Candidate KeysPrimary KeysElements of a Primary KeyRules for Establishing a Primary KeyAlternate KeysNon-keysTable-Level IntegrityReviewing the Initial Table StructuresCASE STUDYSummary
Why Field Specifications Are ImportantField-Level IntegrityElements of the Ideal FieldAnatomy of a Field SpecificationGeneral ElementsField NameLabelParent TableShared ByAlias(es)DescriptionGuidelines for Composing a Field DescriptionPhysical ElementsData TypeCharacter SupportLengthDecimal PlacesInput MaskDisplay FormatLogical ElementsType of KeyUniquenessRequired ValueNull SupportEdit RuleComparisons AllowedOperations AllowedValues Entered ByDefault ValueRange of ValuesSpecification InformationSpecification TypeBased on Existing SpecificationSource SpecificationDefining Field Specifications for Each Field in the DatabaseCASE STUDYSummary
Types of RelationshipsOne-to-One RelationshipsOne-to-Many RelationshipsMany-to-Many RelationshipsProblems with Many-to-Many RelationshipsIdentifying Existing RelationshipsEstablishing Each RelationshipOne-to-One and One-to-Many RelationshipsThe One-to-One RelationshipThe One-to-Many RelationshipThe Many-to-Many RelationshipReviewing the Structure of Each TableElements of the Ideal TableRefining All Foreign keysElements of a Foreign KeyEstablishing Relationship CharacteristicsEstablishing a Deletion Rule for Each RelationshipIdentifying the Type of Participation for Each TableIdentifying the Degree of Participation for Each TableVerifying Table Relationships with Users and ManagementRelationship-Level IntegrityCASE STUDYSummary
What Are Business Rules?Types of Business RulesCategories of Business RulesField-Specific Business RulesRelationship-Specific Business RulesDefining and Establishing Business RulesWorking with Users and ManagementDefining and Establishing Field-Specific Business RulesDefining and Establishing Relationship-Specific Business RulesValidation TablesWhat Are Validation Tables?Using Validation Tables to Support Business RulesReviewing the Business Rule Specification SheetsCASE STUDYSummary
What Are Views?Anatomy of a ViewData ViewsAggregate ViewsValidation ViewsDetermining and Establishing ViewsWorking with Users and ManagementEstablishing ViewsUsing Calculated Fields Where AppropriateImposing Criteria to Filter the DataUsing a View Specifications Sheet to Record the ViewReviewing the Documentation for Each ViewCASE STUDYSummary
Why You Should Review Data IntegrityReviewing and Refining Data IntegrityAt the Table LevelAt the Field LevelAt the Relationship LevelAt the Level of Business RulesAt the Level of ViewsAssembling the Database DocumentationDone at Last!CASE STUDY—WRAP UPSummary
Flat-File DesignSpreadsheet DesignDealing with the Spreadsheet View Mind-setDatabase Design Based on the Database SoftwareA Final ThoughtSummary
When May You Bend or Break the Rules?Designing an Analytical DatabaseImproving Processing PerformanceIs It Worth It?Improving Performance by Other Means FirstDocumenting Your ActionsSummary

Overview

Sound design can save you hours of development time before you write a single line of code. Based on the author's years of experience teaching this material, Database Design for Mere Mortals is a straightforward, platform-independent tutorial on the basic principles of relational database design.

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.

0201694719B04062001

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Start your free trial

Database Design for Mere Mortals®: A Hands-on Guide to Relational Database Design, Third Edition

Publisher Resources

ISBN: 0201694719Purchase book

Database Design for Mere Mortals

by Michael J. Hernandez

Overview

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

You might also like