Data Vault Modeling and Certification

 Data Mo deling  Data Vault Mo deling  Certificatio n  Big Data  Ensemble Mo deling  Agile DW

ENSEMBLE MODELING with Comparison

• Ensemble Modeling • Unified Decomposition • Concept Constellations Temporal Considerations • Anchor Modeling • Data Vault 2G • Focal Point • Hyper Agility • Comparison • Recap

Preface: The Saga of Data Warehousing

Once upon a time data warehousing was becoming more popular and everyone was eager to build their own. But whenever they tried they failed. They called upon their best to fix this but they just couldn’t solve the problem.

They discovered that meeting the needs of the data warehouse meant that the tables got too big and too hard to work with. They just could not handle changes over time. If the smallest thing changed it always meant they had to change the entire table. When just a single attribute was updated they had to insert a record for all of the attributes. All seemed lost.

But around the world there were rebels who questioned the conventional wisdom. And their voices were finally heard: Why not separate the things that change from the things that don’t change?

• The constellation of component parts acts as a whole – an Ensemble

All the parts of a thing taken together, so that

each part is considered only in relation to the whole

Like “Late Binding” for Business Rules based Semantic Integration • With Ensemble Modeling the Core Business Concepts that we define and model are represented as a whole – an ensemble – including all of the component parts

• Breaking out Business Concepts (Entities, Dimensions etc.) into parts – For Flexibility, to facilitate the integration of things that are interpreted in different ways or are changing (updated) independently of each other – For Agility, to facilitate the capture of new or changing schemas including concepts, keys, attributes and relationships Without “Unified” the Decomposition would lead to Table Anarchy

• To keep Concepts together so the DW can support integration and a common standard view of unified concepts

• As Ensembles are decomposed Core Business Concepts, they share with 3NF and Dimensional modeling the key dependency rule:

all things that can be uniquely said for one instance of a concept

• When the Core Business Concept requires multiple (2-n) concurrent instances of certain context attribute(s) then the resulting expanded Ensemble (grouping) is a Concept Constellation

& ANCHOR MODELING

• The most popular of the Ensemble forms, Data Vault modeling is based on the Unified Decomposition of Core Business Concepts into parts containing 1. Business Key Hubs 2. Relationships Links 3. Context Attributes Satellites

• BK in center of Hub • Links all M:M no context • Satellites built for History • Context split out by Design • Based on Core Business Concept

* FOCAL POINT

* HYPER AGILITY

• Ensemble Modeling = Data Warehouse Modeling • Unified Decomposition is the underlying feature • Several variations exist and more will arrive • Select your flavor – then lock down your pattern

• Q&A