From a 3NF to Data Vault – short lesson

This is a very short lesson on the architectural steps necessary to get from a “mostly” normalized model to a Data Vault Model.  It really isn’t that hard after all, and you should have a very good handle on the repeatable process.

Step 1: Identify the natural world keys or the business keys in one or more source models

Step 2: figure out if these business keys actually MEAN the same thing, and represent the same grain of data, if they do, construct 1 Hub for all these keys to land in, if they are different, or defined to represent different things – then they each deserve their own Hub.

Step 3: Take the relationships (foreign keys) from the source model, and in relation to the PK – find out where to build a SINGLE LINK for each set of foriegn keys, keep these keys together as a unit of work.   Build your links in the target model

Step 4: Take the remaining data set, and place it in to Satellites.  Try not to collide or override existing Satellites unless the data really is meant to be combined across source systems.  Be wary of multi-active satellite rows, split the Satellite data by classification (or type) and rate of change.

Step 5: Decide where to attach the Satellites, if the PK of the source table is a composite FK, then the Satellite attaches to the LINK you just built.  If the PK is a single non-FK (composite or not – there’s no FK for the PK fields), then attach it to the corresponding Hub table.

As always, feel free to reply with your questions.

Hope this helps,
Dan L
DanL@DanLinstedt.com

Tags: , , , , ,

No comments yet.

Leave a Reply

*