1. Avoid multiple Joins to the same table Reducing the number of joins to a table is crucial, as each additional join could lead to a full table scan or index access. This can be accomplished by implementing subqueries, volatile tables, or ordered analytical functions. This example showcases how to apply an ordered analytical function …
A Teradata Show Table Proxy for Full DDL Recreation from DBC Throughout my recent development activities, an old desire became relevant again. It goes as follows: Can one write a query that recreates the entire DDL of a table out of dbc views or tables alone? Put differently, can I write my Teradata show table …
Over the years, numerous debates have emerged concerning the superior performance of specific statements: Many personal experiences are often shared but tend to misattribute causality. People usually construct a single test scenario and extrapolate sweeping conclusions from it. The speculation has ceased. Herein lies the truth: The validity of these statements hinges on the data’s …
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. Whatever the reason may …
Expert network for enterprise data platforms. Senior consultants, project teams built for your challenge — across Teradata, Snowflake, Databricks, and more.
📍Vienna, Austria & Jacksonville, Florida
Join 4,000+ data professionals.
Weekly insights on Teradata, Snowflake & data architecture.