After the successful creation of a history layer, it is time to focus on the core parts of the datawarehouse: the Data Vault. In this example a ‘raw’ Data Vault is created: no changes or transformations are done here. The first script in this layer creates the Hubs and the corresponding Satellite. Currently this is done based on the history layer, which is probably not the best approach. It would be better to have the...
3NF architecture BIML Business data vault CBIP data modeling Data Vault Data Vault 2.0 Data Warehouse Driving Key DV2.0 EAI Enterprise architecture Error Bitmap Error handling ESB ETL ETL Automation ETL Framework ETL Generation Hub Informatica inmon Kimball Link Link Satellite Logical Delete Metadata OBW OWB PIT Powercenter PSA Ravos Referential Integrity Satellite SCD2 SQL Server SSIS Staging Area Staging Layer Time variance Virtual EDW Virtualisation XML
Visits since October 2015
Search this site
About this site
Hi! I'm Roelant Vos, working at Allianz Worldwide Partners in Australia. I try to make life easy working with all things data and use this site to share personal ideas and concepts. Feel free to contact me any time!
- Using a Natural Business Key – the end of hash keys?
- When a full history of changes is too much: implementing abstraction for Point-In-Time (PIT) and Dimension tables
- Updated the Data Vault implementation & automation training for 12-14 June in Germany
- When is a change a ‘change’?
- Some insights about … Insights