in this post i introduce ideas and thoughts around why the data vault is easier to make model changes, and why it manages better to handle changes. if you have comments, thoughts, or other experiences i encourage you to add your comment to the end of this posting. as you know, i’ve launched one-on-one coaching, this is the kind of knowledge you get within the walls of one-on-one coaching. but for today – i’m giving you the answers free to show you the kind of value you get when you sign up for my coaching sessions. contact me today: firstname.lastname@example.org for more information.
how does this make model changes easier than in a traditional 3nf model?
this is explained in the tdwi boston slides, it’s also explained inside the coaching area of my site. if you want the full answers, you’ll have to register to receive a 3 month coaching session. the answer is long and drawn out. i can’t explain it in a single sentence, but here’s the basic idea behind it all:
if you’ve ever heard my presentations: you know that the link carries much of the magic. because it’s a many-to-many it acts as a de-coupler between and across tables, so changes to different satellites are “isolated” from other changes in other parts of the model. you would also know that the magic is really about constructing new links and retiring old links as the model changes and moves with the business. this is something that ing real estate is doing in their dynamic data vault that’s hooked directly to their microsoft sharepoint 2010 back-end.
it really has everything to do with the fact that the data vault never implements 1 to many, many to 1, and 1 to 1 relationships in the architecture. the data vault banks on the fact that relationships change over time as business changes – and therefore uses this to it’s advantage. it makes the data vault models “future proof” if there is such a thing…