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. Change history tables are typically complex. …
Situation and Setup of a Historisation in Teradata Vantage Imagine that the time has come to improve your physical data model. Flawed or obsolete Teradata Vantage historisation design decisions need to be corrected. You are asked to separate tables of the same entity with different attributes. We do not question why there are separate tables …
Learn about Teradata’s temporal data management functionality based on TSQL2 specification in this article. Discover how it simplifies historization.
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 are triggering a historisation. A principal motivation for such a move away from a daily snapshot table could be space restrictions. Whatever the reason …
Expert network for enterprise data platforms. Senior consultants, project teams built for your challenge — across Teradata, Snowflake, Databricks, and more.
📍Vienna, Austria & Miami, Florida
Join 4,000+ data professionals.
Weekly insights on Teradata, Snowflake & data architecture.