How Do You Track History?

Concepts: paScdPipeline

Standard SCD Type 2 tracks what the data looked like at each point in time. But the follow-up is: what happens when you discover the data was wrong? A customer's address was entered incorrectly in January, and legal sends a correction in March. Do you update the January record? Insert a new version backdated to January? This is where bi-temporal modeling enters the picture - and where most candidates get stuck. Late Corrections A late correction is a change that should have been applied in the past but arrives in the present. Standard SCD Type 2 cannot handle this cleanly - it only supports closing the current version and opening a new one. If you close the current version and insert a correction backdated to January, you create a gap: the period between the original (incorrect) January re