there literally are no hardware dependencies for using the data vault model, but you still might want to read this entry… i cover why, and expose a small bit of the databases and hardware underneath. 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.
what are the hardware dependencies of this approach?
none. absolutely none. the data vault model is a data modeling technique. like any “data modeling technique” the data vault favors mpp hardware for scalability – but only if or when you actually have “big data needs”. when i talk about big data, i’m discussing data sets that move 1tb per hour, and that have in excess of 80tb in their data vault already…
at the same time, i have a 30gb data vault on a sqlserver instance, windows home vista, amd turion 64 bit – and it’s just fine. i’ve built data vaults on 2cpu oracle boxes, linux hardware, standard servers – with up to 5 to 8 tb of data, and they run fine… so there are no hardware dependencies.
by the way, the world’s smallest data vault (and gives you business value) is one hub + one satellite. talk about scope control.