i was recently asked this question, so i thought it might be nice to share a bit of history. this is a very short entry, explaining how dv got it’s name!
in the beginning, i was working for the us federal government. my customers included the department of defense, national security agency, and nasa to name a few. it was the early 90’s and they had a need to build a data warehouse. however, this warehouse was not to be like any other.
you see, most data warehouses at that time were being built in either 3rd normal form, or dimensional models, but that’s not the crux of it. they were – for all intensive purposes, not data warehouses, but instead, information warehouses. in reality, they loaded all the data post business rule execution (ie: post-munging).
this, in turn, made it extremely difficult for anyone to audit the so-called data warehouse. not to mention, the business users were arguing over business definitions, metadata, and the computations / rules that were applied to the data being “aggregated for the common good / enterprise view”. well, we all know how that turned out… caused lots of pain and so on, but i digress.
i was asked by the dod and nsa to construct an auditable historical data store, they wanted a common unified modeling practice (at the time they were training us on six sigma, cmmi, pmp, and of course rup (rational unified process). to have an “auditable data warehouse” was unheard of, people couldn’t or wouldn’t fathom the notion of storing raw data in an integrated fashion. i fought many of the same battles i still see around today (like: what’s the value of the dv instead / over/above a straight psa?)
anyhow, that’s beside the point. in order to change the culture, and create a unified modeling view, i had to construct something that would allow the nsa to extend / expand the model based on the core design behind closed doors (in the classified areas), and to inherit all the changes as i went along without disrupting any of their additional components that they’ve modified or extended. yes, near-zero impact was a design challenge right from the start!
ok, long story short: i started by calling it “common foundational warehouse modeling architecture” – cfwma. it had all the characteristics, met the needs (more stories about how and why), and so on. but cfwma is not an easily pronounceable acronym (try it, but don’t hurt yourself!).
when i took another look at “what this thing accomplished”, it in fact, did act like a bank vault – keeping data safe & secure in the classified world, and in the commercial space, allowing the data (as needed by log in), to be accessible. an additional requirement i had right from the start was to provide for cell level protection in a relational database space, which doesn’t sound so hard today, but back then – it was tough.
anyhow, we (my team and i) managed to construct this “bank vault like looking thing” called a “data warehouse”, so i was joking one day with my classified sponsor, and he said: you should call it a “data vault” – it made sense to me, so thus, it was named.
before september 11th, 2001, i was the only one utilizing the name on the web – but oracle soon got ahold of it, and after 9-11 they decided it was a cool marketing name for security products. the rest they say, is history.
now, is the “data vault” a place to lock up the data and throw away the key? no, but it does offer secure protection on components of the model that need to be applied. hope you enjoyed this trip down memory lane.