RelationalSample
Data Vault 2.0
Splits every business concept into hubs (keys), links (relationships) and satellites (history). Built for integrating many sources and auditing every change.
Try this
- 01Press “Replay load” and watch the load order: hubs first, then links, then satellites. Each layer only depends on the one before.
- 02Show only Satellites: every descriptive attribute lives here, never on a hub or a link.
- 03Click hub_order: it is joined by two links and one satellite, but holds nothing except the key.
Notation
- Hub
- The list of unique business keys for one concept (every customer id ever seen), plus a hash key, load date and record source.
- Link
- A relationship between hubs (customer placed order). Always many-to-many, so it never needs remodelling when the rules change.
- Satellite
- Descriptive attributes with full history. A new row is inserted whenever the hash_diff of the attributes changes.
- Hash key (HK)
- A hash of the business key, so hubs, links and satellites can load in parallel without lookups.
- Record source
- Which system each row came from, for auditability.
Use it when
- Integrating many source systems into an enterprise raw layer
- Full audit and history requirements
- Sources and business rules that change often
Avoid it when
- Direct reporting (build star schemas on top instead)
- Small, single-source projects where the extra tables are pure overhead