Insights - Page 2 Of 33

Teradata Join Indexes vs. Snowflake Materialized Views — A Technical and Pragmatic Comparison

03/09/202611/25/2025 by Roland Wenzlofsky

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 …

From QueryBand to Query Tag

03/09/202610/28/2025 by Roland Wenzlofsky

How to Track Query and User Activity After Migrating from Teradata to Snowflake By Roland Wenzlofsky · DWHPro 🎯 Why This Matters In Teradata, QUERY_BAND has long been a hidden gem — the ability to tag every query or session with metadata like App, Job, or UserGroup. That little string became the key to workload …

Rounding Differences Between Teradata and Snowflake

03/09/202610/26/2025 by Roland Wenzlofsky

One of the smallest but most persistent sources of data mismatches during a Teradata-to-Snowflake migration comes from an unassuming function: ROUND(). While both systems follow ANSI SQL semantics, they differ in how they handle values that lie exactly halfway between two rounding candidates (i.e., when the digit after the rounding precision is 5). Standard Rounding …

Teradata’s Semicolon Optimization vs. Snowflake’s Architecture — Two Worlds, One Goal

03/09/202610/16/2025 by Roland Wenzlofsky

1. The Forgotten Performance Trick: A Semicolon That Saves Time For decades, Teradata developers have quietly used one of the smallest but most powerful performance optimizations in BTEQ:a semicolon at the start of a line. This isn’t just a style choice.It tells Teradata to combine all statements into one multi-statement request, parsed and executed as …

Understanding Skew in Teradata and Snowflake

03/09/202610/13/2025 by Roland Wenzlofsky

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 …

Why the Same UPDATE Means Something Entirely Different in Teradata and Snowflake

03/09/202610/05/2025 by Roland Wenzlofsky

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. …

Teradata Hybrid: Bridge or Destination?

03/09/202609/30/2025 by Roland Wenzlofsky

For many years, Teradata was the undisputed leader in large-scale data warehousing. Banks, insurers, and telcos built their most critical systems on it. Today, the market is very different. Cloud-native databases such as Snowflake, BigQuery, and Databricks have set new standards in elasticity and simplicity. The question is: what role will Teradata play in this …

Teradata vs. Snowflake: Why GROUP BY Performance Differs at Scale

03/09/202609/27/2025 by Roland Wenzlofsky

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 …

Migrating Bulk Loads from Teradata to Snowflake

03/08/202609/23/2025 by Roland Wenzlofsky

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 euqals 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 …

Skewed Joins, Straight Answers: A Neutral Guide for Snowflake/Teradata Teams

03/09/202609/22/2025 by Roland Wenzlofsky

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 …