Since Datavault Builder was built as a native cloud application from the beginning (with the ability to run on-premise or in the cloud), we are pleased to announce that our customers now have the fantastic ability to use Snowflake db as a data warehousing database.

In this article I describe why you could use multi active satellites in your Data Vault, why you probably shouldn't in most cases and how you can do it if you have to: use a document satellite design to prevent granularity issues down the road.

In this article I’m discussing only links representing transactions. I deliberately exclude links which represent relations (i.e. master data relations = giving context to an object like the link between a city and a commune). I highlight the challenges of the existing design and propose to always use a hub to define the granularity of a link.