Anti-pattern: Using a HASHKEY to generate the LINK HASHKEY
Anti-pattern: Including Business Keys in the SAT HASHDIFF
Anti-pattern: Adding column to the middle of the hashdiff
Anti-pattern: Using Multi-Active SAT to model data with multiple records for the same Business Key that arrive one Micro-batch
Anti-pattern: Having two or more records in a SAT for a Single Business Key with the same LOAD_DATE
Anti-pattern: Adding Relationship Temporality to a Non-historised LINK
Anti-pattern: Excluding the Dependent Child in the generating the LINK Hashkey
Anti-pattern: Using Historized Links to store Transactional data that does not change
Anti-pattern: Implementing Business Rules at the Infomart Level
Anti-pattern: Creating Hubs for Dependent Children
Anti-pattern: Using varchar to store the HashKeys and HashDiffs
Anti-pattern: Load Dates that are anything other than time of loading the Staging