short entry discussing some of the highlights of two specific data vault loading approaches.
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.
here we discuss the impact of “additional tables” on etl jobs. it really is negligable, but in this case – it would be good for you to read this entry.
this entry discusses the age-old-question of etl performance – a data vault approach and a traditional approach.
this post discusses in brief, what the etl implementation for a data vault might look like.
satellite load code example in oracle warehouse builder (omb) script.
short excerpt on existing issues i’m finding, and incosistencies in the omb/owb product.
omb/owb data vault link code generated from a couple simple inputs.
this is a look into tidbits of implementation for structures in omb/owb code.
i’ve long held a belief that the data vault modeling style ushered in a new era, that being one where we have the power to dynamically accept and automatically absorb new data elements. of course, as always there are some rules and regulations (patterns) around when and how this can happen, and when the modeling […]