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 […]
unfortunately the world today wants to mistakenly compare and contrast chickens and ducks. well i am in the process of writing a full compare and contrast white paper that i will soon release that i hope goes through all the right points. this post will cover just a few points – if you are a) […]
i’ve been considering many of these questions over the years, and now would simply like to share a few thoughts about the basic nature of the data vault model. i hope in future posts to share additional thoughts about the methodology. in this post, i will try to return to basics. try to explain what […]
there seems to be an interest (again) in having a short and simple “business value” definition of the data vault model & methodology. that said, i will do my best to list it as succinctly as possible. however, i would love to hear your thoughts on what you think is business value, and whether or […]
once again my friends, someone has decided to put an interesting entry up asking the age old question: why is data vault model so important? along with several other questions, they admitted they cannot see the value. however, the author posted his words not in an attacking type of manner (as others have done in […]
people come to me all the time complaining about the number of joins in the data vault. i thought i might take a crack at answering this question/complaint, and provide some solid mathematical proof behind the fundamental design of the data vault model. i welcome your feedback (i hope you take the time to comment).
there are a lot of comments, and questions out there about the data vault model, particularly from those who claim to know it and understand it. yet some of them have a) not engaged me, nor b) gone to take the certification class. reasons for the dv model are buried in the methodology – a […]
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.
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.
i begin to examine why the star schema or dimensional modeling technique doesn’t really meet the true needs of enterprise data warehousing. if you’ve succeeded with a dimensional model at an enterprise level, please add your comments, i’d love to hear from you.