Saqib Ali

Data Vault Anti-pattern: Using Multi-Active SAT to model data with multiple records for the same Business Key that arrive one Micro-batch

When using a Change Data Capture (CDC) tool it is possible to get multiple records for the same Business Key in a single micro-batch. Loading this data as-is will will result in multiple records for the same Business Key for the same LOAD_DATE. This is the incorrect loading pattern. A regular Satellite should have only Data Vault Anti-pattern: Using Multi-Active SAT to model data with multiple records for the same Business Key that arrive one Micro-batch

Data Vault Anti-pattern: Having two or more records in a SAT for a Single Business Key with the same LOAD_DATE

A Satellite, by definition, should have only one record per Business Key per Load Date. The Business Key (or the hash of the Business Key) + LOAD_DATE is the unique key for the record. BK + LOAD_DATE is the Primary of the SatelliteThe exception is a Multi-Active Satellite where a Sequence Number is added to Data Vault Anti-pattern: Having two or more records in a SAT for a Single Business Key with the same LOAD_DATE

Data Vault Anti-pattern: Using Historized Links to store Transactional data that does not change

Transactional Data that does not change e.g. sensor data, stock trades, call center call data log, medical test results, event logs etc. should reside in a Non-historized Link (NHL) aka. Transaction Link. There is no point in using a Historized Link to store data that can not change.  All of the attributes of the Transaction Data Vault Anti-pattern: Using Historized Links to store Transactional data that does not change

Data Vault Anti-pattern: Implementing Business Rules at the Infomart Level

While it is tempting to implement Business Rules at the Infomart Level, that is not where the Business Rules should reside. They should reside in Business Vault. This enables historisation of the Business Rules and introduces auditability. When the Business Rule changes, with historisation it is possible to go back in time and analyze the Data Vault Anti-pattern: Implementing Business Rules at the Infomart Level