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.