18
Design for the Future The Future of Data For the DBA

Design for the Future The Future of Data For the DBA

Embed Size (px)

Citation preview

Page 1: Design for the Future The Future of Data For the DBA

Design for the Future

The Future of Data

For the DBA

Page 2: Design for the Future The Future of Data For the DBA

Reducing empty space and increasing flexibility by clustering around entity types and attribute groups

Page 3: Design for the Future The Future of Data For the DBA

Real world entities have many possible simple relationships.

Simple General-Purpose Relationship Table

Page 4: Design for the Future The Future of Data For the DBA

Multiple entity tables. N2 possible relationships.

Page 5: Design for the Future The Future of Data For the DBA

Putting everything with options into the same entity table leads to lots of unused space.

Old Entity Table

Page 6: Design for the Future The Future of Data For the DBA

Attributes are equivalent to relations.

Relationship Types are also entities.

Page 7: Design for the Future The Future of Data For the DBA

Change the Entities to Phrases.

Change the Relations to Semantic Triplet Sentences.

Triplet Sentence Table Phrase Table

Page 8: Design for the Future The Future of Data For the DBA

Phrase Table Allows any data type

in any “cell”.

Common value types are pooled and indexed.

ValueFloatTable

Page 9: Design for the Future The Future of Data For the DBA

Phrase Table

Used for Project management, Security filtering

Used for metadata in the style of “(S1) was captured by (Device19)”.

Page 10: Design for the Future The Future of Data For the DBA

This table requires either more phrases in a sentence or more sentences.

Complex Relationship Table Example

Page 11: Design for the Future The Future of Data For the DBA
Page 12: Design for the Future The Future of Data For the DBA

Allows more phrases per sentence, more phrases per syntax position, and more syntax positions (metadata).

Now you can select “tables” and “columns” the same way as rows.

Page 13: Design for the Future The Future of Data For the DBA

Value Sentence Table

The sentence table can now hold any complex relationship.

Page 14: Design for the Future The Future of Data For the DBA

The old design pattern - meaning is dependent on the row and column positions in each table.

The new design pattern - pieces of Equal Format Data.

This Old Table

Tables of Equal Format Data

Page 15: Design for the Future The Future of Data For the DBA

Atomic data can be modified non-destructively more efficiently with less locking.

Nondestructive storage can maintain a running snapshot

Common container types reduce N2 complexity in coding, point-to-point conversions and messaging.

Development is de-linked from structural dependency.

Reusable structures encourage reusable code and common dictionaries.

Atomic data enables multiple inheritance

Page 16: Design for the Future The Future of Data For the DBA

There are many ways to say it – keep it simple.

Try to be less ambiguous and use stricter and simpler syntax.

It’s easier to change the vocabulary than change the structure.

More wordiness uses space but adds meaning.

Compared to traditional design, it uses more space per cell when nonempty, but no space per cell when empty.

Repeat the container as multiple “subsystems” to tune the structure

Page 17: Design for the Future The Future of Data For the DBA

Master Data Storage

Messaging Systems

Data Warehousing, Data Marts, and Data Mining

Security, Auditing, Quality Control

Merging Legacy Information

Facility Data and PLM Data

Engineering Project Management

Product Catalog Data

Development Infrastructure

Page 18: Design for the Future The Future of Data For the DBA

[email protected]

+1 (734) 878-0109 voice+1 (734) 878-0684 fax

www.datura-llc.com

Datura, LLCPO Box 498Howell, MI 48844-0498USA