Building a Data Vault with ODE v2 - OptimalBI/optimal-data-engine-mssql GitHub Wiki
Data Vault with ODE
Data Vault is a Data Warehousing methodology. Learn more about it here. ODE is a config-driven engine for building and managing Data Vaults.
At the moment ODE only works with MS SQL Server. Refer here for ODE installation.
Modelling a Data Vault with ODE
Refer our approach for ODE Data Vault structure. This article describes ODE DV objects naming convention you can follow.
Configuring with ODE Refer a quick start to build your first Data Vault ensemble based on Adventure Works table in a few minutes.
Ready to start with the real data? Use this article to configure a Hub and Satellite. Then use this article to configure a Link.
Want to understand how it all works? Follow the step by step instruction to configure DV objects, source table and hook them together.
Managing the Data Vault with ODE
Once DV is configured, build physical tables.
ODE engine allows scheduling the data loads and releasing configuration to another environment.
Query builder could help with selecting the data from Data Vault.
Frequently Asked Questions
Got stuck? Maybe one of the following articles could help.
ODE Config structure
ODE Entity Relationship diagram
Hubs
Should Business Keys be Stored as Concatenated Keys or Separate Fields in the Hub?
Links
How To Implement a Link in ODE?
Where do you Store Point in Time for Information for a Link
Why do Queries, used to load Links often use DISTINCT?
Satellites
How Does ODE Deal with Start / End Dating of Satellites
Should the Business Keys be retained on the Satellite?
What are Tombstone Rows and why does ODE have them?
Why do we use specify a Unique Row Key on Satellite Tables?
Why do we Record the Source of each Row in a Satellite?
Why do we Capture all Column Detail in the Configuration Database?
Delta load
Release
How To Do an Incremental Release
Business rules
Physical tables