1. Design for the Future The Future of Data For the DBA

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

3.  Real world entities have many possible simple relationships. Simple General-Purpose Relationship Table

4.  Multiple entity tables.  N 2 possible relationships.

5.  Putting everything with options into the same entity table leads to lots of unused space. Old Entity Table

6.  Attributes are equivalent to relations.  Relationship Types are also entities.

7.  Change the Entities to Phrases.  Change the Relations to Semantic Triplet Sentences. Triplet Sentence TablePhrase Table

8.  Allows any data type in any “cell”.  Common value types are pooled and indexed. ValueFloatTable

9. Phrase Table  Used for Project management, Security filtering  Used for metadata in the style of “(S1) was captured by (Device19)”.

10.  This table requires either more phrases in a sentence or more sentences. Complex Relationship Table Example

12.  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.

13. Value Sentence Table  The sentence table can now hold any complex relationship.

14.  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

15.  Atomic data can be modified non- destructively more efficiently with less locking.  Nondestructive storage can maintain a running snapshot  Common container types reduce N 2 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

16.  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

17.  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

18. sales@datura-llc.com +1 (734) 878-0109 voice +1 (734) 878-0684 fax www.datura-llc.com Datura, LLC PO Box 498 Howell, MI 48844-0498 USA