Would like to seek guidance on how do you go about separating different layers of data vault in database schemas?
Schema names such as
STG.<> for staging tables
RV.<> for raw vault
BV.<> for business vault
IM.<> for info mart
Is above a good strategy?
Has anyone separated the data in raw vault based on the data domains, e.g. schemas such as customer, employee, asset etc ? If yes, how has been your experience of doing so?
You could, but I wouldn’t split the DV in that way.
The above image shows business domains across a DV – extending an enterprise DV with private BVs. You could build data domain views over that contact but I think that should live in the IM layer
I personally would hold all Data Vault objects in one database, and the reporting / mart layer in another. It’s less noise and end users shouldn’t be able to view any of the data vault objects anyways.
You could even have a DB/mart per department if you’d like. It really depends on your organization needs.