I’ve had the pleasure recently of discussing this topic both publicly and privately with all kinds of people in the Data Vault community. For this, I say thank-you for all your wonderful insights. I now see a bit where the confusion lies (ie: what is and is not a Data Vault), what are the acceptable modifications? can I make modifications and still call it a Data Vault? how do I use and leverage the DV techniques without “being so rigid”, and yet make them work for my customers?
The only class that I will be teaching in 2014 in the US, for Data Vault 2.0 Boot Camp and Private Certification will be in September, in Kentucky with my partners: Clear Measures. I encourage you to sign up, seats are filling up fast.
There has been a lot of discussion around this idea lately, and it seems the community is finally ready to actually contribute. In that light I’ve started a FREE wiki site for collaboration on the Data Vault Modeling Standards, join today, and have some fun!! (no, there is nothing out there yet, feel free to create to your hearts content).
This post covers my opinion in what people today call a data lake. I will discuss what I think needs to be done to clarify the terms, and why if left unmanaged, it quickly turns in to a data junkyard or polluted data lake. On the flip side of the coin, today there is still valuein leveraging your existing relational database for your Data Vault data warehouse. Read more…
In recent times, there have been several discussions around the standards of the Data Vault Modeling components. In fact, this isn’t the first time (nor the last) that I expect the standards to be challenged. That said, I feel it necessary to discuss just what I put the standards through before publishing, in hopes that if you feel the urge to suggest changes, you can apply the same rigor as I do before telling the user group that “I’m wrong, the standards don’t work and here’s a change”. This is a post in to the reasoning behind, the insight and the rigor applied to the standards (ALL standards) for the Data Vault 1.0 Model, and Data Vault 2.0 Model. Read more…
Recently I taught a class on-site for a customer all about Data Vault 2.0. When I got to the point where I shared the template / process for end-dating (updating end dates in place, using a characteristic function) I was point-blank told: “Teradata does not use or have indexes other than the Primary Index” And that it would subsequently do a full table scan every time we wanted to execute a select from a satellite where the end date is NULL and has at least 2 or more “active” rows.
Data Vault 2.0 and the world of Data Vault is expanding!! You are encouraged to join the Data Vault Movement… come find out why it’s important, relevant, and carries business value in the ever changing world of Data Warehousing and Business Intelligence. Come find out why it meets Big Data needs, and addresses NoSQL seamlessly – leveraging your existing environment without throwing away sunk costs and knowledge in relational technology.