Clear all

How should we evolve a Hub and it's keys?

Posts: 482
Topic starter
Joined: 3 years ago

The topic was raised by a number of people at the conference in 2019.  The topic is:

Suppose we have a Hub, and it currently integrates 2 source systems.  A 3rd one appears with a different key structure, it's the same grain, same semantic meaning, it just has multiple fields representing it, where the other two source systems have only one field representing the business key.

The question is: how do we suggest to handle this?   Before I provide an answer, I want to see what YOU think.  Please reply - there is NO wrong answer, just suggestions on this.

The caveat or caution is: How do we avoid: "hubitus" and "source system data vault syndrome".

33 Replies