Question

There is a HUB_CUSTOMERS which holds three different satellites with customer data from three different sources. Therefore the RECORD_SOURCE is a part of the composed key in HUB_CUSTOMERS. The sets (satellites) are not disjunctive.

Now we have to prioritize the source data to integrate the customer data in a three-step process to generate a business hub e.g. BHUB_CUSTOMERS (B=Business) which holds the customers and represents our main source table for e.g. DIM_CUSTOMERS in a data mart. By this we create redundancy: HUB_CUSTOMERS and BHUB_CUSTOMERS.

Is this approach okay?

Answer 1

Hi Raphael,

first of all, the record source should not be part of the business key. It should be there for debugging purpose only. You can however, add a field to the composite key to reflect the source system.  This has been discussed on p age 124 of our book (Building a Scalable Data Warehouse with Data Vault 2.0).

In the end, the idea is that the Hub integrates the data from your satellites using the business key.

You should consolidate your keys using a same-as-link (page 129).

Hope that helps,

Michael