Skip to the content

Data Vault 2.0

DV2 Data Warehouse Methodology

Recent Posts

  • Bitemporal data in Data Vault
  • Data Vault Anti-pattern: Using a HASHKEY to generate the LINK HASHKEY
  • Data Vault Anti-pattern: Including Business Keys in the SAT HASHDIFF
  • Data Vault Anti-pattern: Adding column to the middle of the hashdiff
  • Data Vault Anti-pattern: Using Multi-Active SAT to model data with multiple records for the same Business Key that arrive one Micro-batch

Recent Comments

No comments to show.

Data Vault Anti-pattern: Creating Hubs for Dependent Children

Saqib Ali | February 28, 2022
Dependent Children should not have their own Hubs. They are not Business Concepts and as such should not be a Business Key by themselves. They only make sense when associated with a Business concept. One example is Line Items in a Order. The Line Item in Order by itself does not make sense. It needs to … Data Vault Anti-pattern: Creating Hubs for Dependent Children

Data Vault Anti-pattern: Using varchar to store the HashKeys and HashDiffs

Saqib Ali | February 24, 2022
Why would you do that? HashKeys and HashDiffs are binary generated using a hashing algorithm like MD5 or SHA-1. Just store them as binary and effectively halve your storage and double your I/O! No need to convert them to the Char to store them as Varchar.

Data Vault Anti-pattern: Load Dates that are anything other than time of loading the Staging

Saqib Ali | February 22, 2022
By using the Load Date we should be able to identify all the Data that was loaded into DV in that particular batch. If the Load Date is some else, for e.g. the Load Date from the ETL tool, the entire batch in DV can not identified using the Load Date.

Posts navigation

newer →
email saqib@dv2.org for guest post submissions