Roelant Vos Data solution design patterns, implementation, and automation

end-dating 0

A not-so-gentle follow-up on bitemporal data challenges

When delivering data from the integration layer (e.g. a Data Vault model) to the presentation layer (anything, but usually a dimensional model or wide table), a key requirement is re-organising data to the selected ‘business’ timeline for delivery.

During this process, we leave the safety of the assertion (technical) timeline behind and start using the real-world state timeline for delivery. This may create some unexpected results!

0

A gentle introduction to bitemporal data challenges

The data is wrong! No, it’s not wrong, we’re just looking at it from different points in time. This post shows how a data warehouse helps to manage this common topic on data interpretation.

0

Deterministic dimension keys in a virtual Data Vault

When preparing Data Vault content for consumption in a dimensional model, dimension keys can be created to join the resulting fact- and dimension tables in a performant way. But what about for a truly virtual data mart? This post covers approaches to issue dimension keys that are fully deterministic.

0

Trying out Data Vault code generation just got even easier!

To facilitate ongoing research in tweaking Data Vault patterns for various use-cases, I recently updated the open source data warehouse automation environments TEAM (source-to-target mapping management) and Virtual Data Warehouse (code generation). These updated versions make playing around with patterns even easier. If you’re interested in having a look at how different patterns work, or what it would mean to deploy a fully virtual data warehouse – have a look at the provided examples. With...