I’ve been reflecting on recent events, and having some great discussions with many of you in the community. For that, I thank-you. I wanted to take a minute to return to the roots of the Data Vault, and why it was created in the first place. I will also do my best to provide a non-biased (even though you think I may be) minor comparison of the Kimball / Data Vault statements going around the industry.
I’ve begun researching Data Vault models on Hadoop solutions, including HadoopDB and Hive. Recently I came across a number of articles which describe the solutions of Hive and HadoopDB in detail on top of Hadoop solutions. I had to take a minute to write this article, to explain my view points of using the Data Vault model on a Hadoop Solution. I also explain where the Data Vault Model fits in the NoSQL or Non Relational world, and why it’s still relevant. Furthermore, I touch on the changing nature of certification – why it’s not so relevant any more.
Super Charge your Data Warehouse (my technical Data Vault Modeling Book) is now available on Amazon for those that want it. I am working on releasing it to Kindle, and iTunes libraries.
The Data Vault Model is NOT the be-all-end-all solution to data warehousing, it IS a single evolutionary step forward, as it is a Hybrid design. If you don’t feel pain in your current implementation, then you may not be a candidate for the Data Vault model and methodology.
Warning: This post is not for the faint-of-heart who are easily offended. This post is a short life-lesson about my cat, doing the same thing over and over again. And how, I’ve experienced life in Business Intelligence projects around the world – doing the same thing over and over again and yet, expecting different results.
A long written response to a well-thought out comment about a successful Dimensional Data Warehouse. Including the values and benefits of the Data Vault.