Business vault is the area where we persist the business logic output built in our data warehouse as satellite and link tables. Not hub tables, hub tables are populated from the source system, business vault links and satellite tables merely extend an existing raw vault using the same patterns available to raw vault. This means, BV can be captured as:
Business vault link tables capturing the relationship between business entities derived within the data warehouse. This includes, same-as and hierarchical relationships.
Business vault satellite tables in the many variations we already support in raw vault, such as regular satellite, satellite with a dependent-child key, multi-active satellites, partitioned multi-active satellites, non-historized satellites (or links) and hybrid satellites. If you have derived business logic to determine relationships effectivity, record status or tracking record occurrence then these can be persisted as business vault satellites as well.
The business logic can be written in any language you choose SQL, Python, JavaScript or whatever application logic suits your scenario (we’ve even built logic into jar files and persisted that a business vault link here!). Depending on the use case, the pragmatic data vault deploys business vault in one of two ways (and both can exist within the same deployed data vault…
