- Non-temporal satellite
- Primary key: Hub-FK, EventTime
- Uni-temporal satellite
- Primary key: Hub-FK, AssertionTimeFrom
- Further columns: AssertionTimeBefore (note: assertionTimeBefore instead of assertionTimeTo as better naming for an open interval)
- Bi-temporal satellite
- Primary key: Hub-FK, AssertionTimeFrom, StateTimeFrom
- Further columns: AssertionTimeBefore, StateTimeBefore
- Hans Hultgren spoke about multi-structured data and how to model it regarding tools like Hadoop or Kafka for streaming requirements. Data integration means change. Change is ever-present and unstoppable. Agility is a measure of an enterprise’ ability to adopt change and a primary feature of the DWH. Germany is currently the fastest growing Data Vault market.
- Kent Graziano (who also started the second day with a morning Chi Gung activity session) spoke about a Hybrid Data Vault case study with a migration from a 2-layered, Kimball-style DWH to Data Vault. He showed the downsides of a 2-layered DWH when new sources are added. The solution was a 3-layered architecture with a Core Warehouse Layer for data integration by business keys.
- John Giles spoke covered multiple Data Vault challenges around business keys and the requirements to record existence over time. He compared record tracking and status tracking satellites and their usage for his requirements.
- Roelant Vos had a one-hour session and a full day workshop covering Data Warehouse Automation. The ultimate goal is the persistent staging area with a virtualization on-top.
— TheRealDataArchitect (@FSDataArchitect) 27. Oktober 2017