DWHPro Insights

Historization

Teradata – Merging two change history tables

Illustration of a glossy orange database cylinder with data fragments across its surface

Have you encountered a poorly designed physical data model where object columns are distributed randomly across tables, and you wish to unify them in their rightful place? Merging non-historical tables is simple, but the process becomes more complex when historization is applied to at least one of the tables. The fragments below illustrate interval overlap; …

Read more

Enhancing Your Teradata Vantage Design with Teradata Historisation: A Comprehensive Method Popular

Illustration of a glossy orange database cylinder with data fragments across its surface

Situation and Setup of a Historisation in Teradata Vantage This article presents a conceptual classification of history transformations. The original SQL templates are incomplete and are not a validated migration solution. In particular, grouping solely by repeated attributes can merge separate A-B-A intervals and gaps; a correct implementation must identify contiguous islands for each business …

Read more

Teradata Historisation – Daily snapshot to change history

Illustration of a glossy orange database cylinder with data fragments across its surface

For various reasons, we may need to switch our Teradata historisation from snapshot tables to a start date/end date logic table, which I usually call a change history, as only changes trigger a historisation. A principal motivation for such a move away from a daily snapshot table could be space restrictions. The former full conversion …

Read more

Protected by Security by CleanTalk and CleanTalk Anti-Spam