to all those interested, i have some great news! i am announcing new certification channels, and new methods of becoming certified. i am also announcing the arrival of data vault 2.0.
about data vault 2.0
its time for an evolution to the modeling techniques. i’ve spent the past 3 years working on data vault sites around the world. i’ve also been working with multiple platforms, performance issues, join issues, and basic data set physical issues. well the time has come – after reviewing all your posts on linkedin, all the e-mails i’ve received, and all of the client sites i’ve visited – i now see there is a need for additional changes to the physical structures of the data vault. so i am announcing dv2.0.
data vault 2.0 brings with it some needed changes to the structures for dramatically increased performance, along with removal of joins along the way – while maintaining the integrity of the modeling architecture. these changes to the physical structures will help with performance across the board (from query to etl performance) to query performance, to partitioning. yes, additional partitioning options will also be available with the changes. i’ll give you a hint: bridge tables will no longer be needed to span link queries – eliminating the need for data replication to yet another structure. i’ll give you another hint: there will be no difference in handling delta inserts versus delta updates, they an now be executed in a single etl pass (sql pass). i’ll give you another hint: multi-active satellite rows will resolve themselves very very easily.
more to come later on the dv2.0 specification. i will also be releasing all kinds of downloads to the students in my on-line data vault training portal, the downloads will be focused around the methodology and the project plan.
will i lose my existing investment in my current data vault?
no. the dv2.0 structure changes are incremental. your existing investment can still exist, it will be easy to alter the structures to conform to the dv2.0 specification, and it’s backward compatible. in other words, once you alter the structures, you can apply the changes to all the historical data in the dv to reap the benefits! note: it does require more disk space, unless you turn on table compression – but i’ve said too much. more to come in the fully released dv2.0 specification in the future. so watch this space!
if you have questions about the upcoming dv2.0 specification, or you would like to submit your ideas for changes you would like to see, then please respond to this posting by submitting your comments.
will there be new standards documents published for dv2.0?
yes, there will be updated standards and rules documents for dv2.0.
you can watch for more information at: http://datavaultalliance.com/training