If you have spent any amount of time working with Teradata, you know that the Primary Index is one of the most important design decisions you make. It determines how data is distributed across AMPs and whether your joins are fast or slow. Choosing the wrong Primary Index is one of the most common causes …
Migration success stories are everywhere. A quick search reveals case studies of companies that moved from Teradata to Snowflake and achieved faster queries, lower total cost of ownership, and happier analysts. Vendors publish them. Consultants reference them. Conference speakers present them as evidence that the migration path is well-trodden and safe. These stories are not …
Most organizations approach a Teradata-to-Snowflake migration as a translation exercise: convert the SQL, move the data, and validate the results. The technical migration succeeds. Then the first quarterly bill arrives at double the projected budget, dashboards queue for 20 minutes during batch windows, and data-loading pipelines that ran in 45 minutes on Teradata now take …
Introducing DWHPro Query Master: A Modern Web-Based Alternative to Teradata Studio As Teradata professionals, we’ve all been there: waiting for Teradata Studio to launch, dealing with Java updates, or struggling with its dated interface when all we want to do is run a quick query. That’s why I’m excited to introduce DWHPro Query Master – …
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 …
At first glance, an UPDATE looks universal.In reality, it’s one of the most misleading similarities between Teradata and Snowflake.The SQL is the same, but the storage, logging, recovery, and performance mechanics are completely different. If you’re migrating from Teradata to Snowflake (or running both), understanding these differences prevents slow jobs, unnecessary costs, and avoidable outages. …
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 …
Big files, real risks, and how not to overspend On Snowflake, COPY INTO scales with the number of files, not the total GB. A single big file equals one unit of work. To go fast and cheap, publish many medium parts (about 100–250 MB compressed), size the warehouse to the files in flight, and use …
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 …
Introduction to the Teradata AMP Worker Task The Teradata AMP Worker Task or AWT is the heart of the AMP, responsible for executing tasks and ensuring the smooth functioning of the system. AWTs are threads that process incoming tasks in the AMP. Each AMP has a finite pool of AWTs, which is shared among all …
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.