This guide collects the material on this site about how Teradata behaves underneath the SQL — what the database does when it is under pressure, how it protects and isolates data, and the operational details that only matter until the day they matter a great deal. Workload Flow Control and DBC.ResUsage The DBC.ResUsageSAWT table serves …
Teradata gives you more than one way to store the same data in less space, and they behave very differently once queries start reading it back. This guide brings together the compression material on this site: what multi-value and block level compression each do, how to find the columns worth compressing, and the trade-off you …
Most Teradata performance problems are designed in long before anyone writes the query. This guide collects the physical design material from this site — the data model, the staging and preparatory layers, partitioning choices, and the MAPS feature — into one reference, starting with the mistakes that cause the most damage. Seven Sins That Destroy …
The cheapest Teradata tuning available is almost never a new index. It is rewriting the query so the optimizer has less work to do and better information to do it with. This guide gathers the query-rewriting material from this site into one place: full worked examples first, then the individual operators and patterns that repeatedly …
Almost every bad Teradata query plan traces back to one thing: the optimizer estimated the wrong number of rows. This guide collects everything on this site about statistics and cardinality estimation — what the optimizer does with the statistics you give it, how it copes when they are missing or stale, and how to diagnose …
Database features should be compared based on their documented behavior, their operational impact, and the architectural principles behind them. This applies especially to physical optimization structures such as Teradata Join Indexes (JIs) and Snowflake Materialized Views (MVs)—two features often mentioned together during migration planning, yet substantially different in scope and design. The intention of this …
Performance degradation caused by uneven workload distribution is one of the oldest and most persistent challenges in parallel data warehouse systems. Both Teradata and Snowflake can experience this imbalance, commonly known as skew. Although the term is shared, the mechanics differ fundamentally: Teradata can suffer from both persistent and runtime skew, whereas Snowflake’s skew occurs …
When migrating analytical workloads from Teradata to Snowflake, one subtle but important performance factor often gets overlooked: how the two systems handle GROUP BY operations on huge tables. The SQL looks the same, but the execution engines behave differently. If you’ve relied on Teradata for years, you may be surprised by Snowflake’s behavior. GROUP BY …
Snowflake’s physical join execution is predominantly hash-based. In practice you’ll observe hash-join variants with two distributions: If you come from Teradata, the intent will feel familiar: both systems aim to co-locate equal keys before matching. This article explains Snowflake’s strategies, maps them to Teradata’s (including dynamic plan fragments), and shows how to recognize and mitigate …
Running out of free Cylinders in Teradata Encountering a situation where free cylinders are exhausted is a significant concern when managing a system, and no more Teradata Space is available. It’s an issue that can adversely impact the operations and efficiency of the database, leading to potential slowdowns or even complete halts in data processing …
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.