Advertisement

Usage-Driven Database Design

From Logical Data Modeling through Physical Schema Definition

  • George Tillmann

Table of contents

  1. Front Matter
    Pages i-xxiv
  2. Introduction

    1. Front Matter
      Pages 1-1
  3. Logical Data Modeling

    1. Front Matter
      Pages 13-13
    2. George Tillmann
      Pages 15-22
    3. George Tillmann
      Pages 23-43
    4. George Tillmann
      Pages 45-67
    5. George Tillmann
      Pages 69-97
    6. George Tillmann
      Pages 99-117
    7. George Tillmann
      Pages 119-131
  4. Physical Schema Definition

    1. Front Matter
      Pages 133-133
    2. George Tillmann
      Pages 135-164
    3. George Tillmann
      Pages 165-184
    4. George Tillmann
      Pages 185-209
    5. George Tillmann
      Pages 211-231
    6. George Tillmann
      Pages 233-256
    7. George Tillmann
      Pages 257-285
    8. George Tillmann
      Pages 287-300
    9. George Tillmann
      Pages 301-314
  5. Where from Here?

    1. Front Matter
      Pages 315-315
    2. George Tillmann
      Pages 317-326
  6. Appendixes

    1. Front Matter
      Pages 327-327
    2. George Tillmann
      Pages 329-347
    3. George Tillmann
      Pages 349-351
    4. George Tillmann
      Pages 353-357
    5. George Tillmann
      Pages 359-360
    6. George Tillmann
      Pages 361-363
  7. Back Matter
    Pages 365-374

About this book

Introduction

Design great databases—from logical data modeling through physical schema definition. You will learn a framework that finally cracks the problem of merging data and process models into a meaningful and unified design that accounts for how data is actually used in production systems.

Key to the framework is a method for taking the logical data model that is a static look at the definition of the data, and merging that static look with the process models describing how the data will be used in actual practice once a given system is implemented. The approach solves the disconnect between the static definition of data in the logical data model and the dynamic flow of the data in the logical process models. 

The design framework in this book can be used to create operational databases for transaction processing systems, or for data warehouses in support of decision support systems. The information manager can be a flat file, Oracle Database, IMS, NoSQL, Cassandra, Hadoop, or any other DBMS.

Usage-Driven Database Design emphasizes practical aspects of design, and speaks to what works, what doesn’t work, and what to avoid at all costs. Included in the book are lessons learned by the author over his 30+ years in the corporate trenches. Everything in the book is grounded on good theory, yet demonstrates a professional and pragmatic approach to design that can come only from decades of experience.
  • Presents an end-to-end framework from logical data modeling through physical schema definition.
  • Includes lessons learned, techniques, and tricks that can turn a database disaster into a success.
  • Applies to all types of database management systems, including NoSQL such as Cassandra and Hadoop, and mainstream SQL databases such as Oracle and SQL Server

Keywords

database design data modeling Entity-relationship physical database design usage maps tradeoff triangle logical data model logical design normalization physical design process model data warehouse

Authors and affiliations

  • George Tillmann
    • 1
  1. 1.Ship BottomUSA

Bibliographic information