327 technical articles on Teradata, Snowflake, Databricks, SQL tuning and data warehouse architecture — written from production experience, not vendor decks.
The historical threshold and performance results below have not been reproduced on the current release. A 20,000-row functional check confirmed that the former decimal literals 19.332 and 19.333 both selected only integer keys through 19, while 19332 selected keys through 19,332. The SQL cutoffs have been corrected. Teradata NUSI Selectivity and Data-Block Density The goal …
Teradata Statistics Histograms – A Short Introduction Many are familiar with the Optimizer’s statistical confidence levels. I was recently surprised to discover that a “high confidence” rating does not guarantee a fully accurate estimation (provided the statistics collected are not stale). While I remain hopeful that my observations may be attributed to a bug, I wanted …
A historical perspective on Hadoop, MapReduce and Teradata SQL-H integration. Assess current capabilities and support before selecting an integration approach.
Have you ever experienced extended waiting times for a table comparison to yield results? Have you ever been compelled to halt and defer quality checks on sizable tables owing to excessive resource utilization during a previous attempt? Hash comparison can be a compact preliminary screen, but it can miss real differences. It must not be …
Introduction to Teradata Data Types Further Data Type considerations require occasional attention to additional issues. Happenstance Nullability Strive for nullability settings that adhere to the data model and are consistent throughout all tables. Allowing mandatory columns to be left open for null entries incurs costs for both storage and optimization. An additional presence bit per …
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. The fragments below illustrate interval overlap; …
Collect Statistics in Teradata – The Evaluation After collecting every combination considered necessary and helpful, you can check the result of the collected statistics on a table by looking at Consider the lengthier collection time when planning maintenance and scheduling, even within regular or optimal conditions. Simplify and maintain the collection method, particularly for smaller tables …
The plans below are historical illustrations. The corrected character-set table definitions and a small join were executed, but the historical row counts and performance were not reproduced. Spool payload calculations exclude row overhead and must not be used as capacity guarantees. Introduction Teradata offers several methods for conducting joins, but all necessitate one prerequisite. The …
This is a historical Teradata 14.10 case study. The small current-release fixture confirmed that the two DELETE variants preserved the same tested rows; it did not reproduce the historical runtime gain. The abbreviated histogram and plan excerpts are explanatory output, not executable setup scripts. The Art of Teradata Performance Tuning As a Teradata Performance Tuner, …
We count visits without cookies and without storing anything on your device. With your permission, we also use Google Analytics for our Google Ads integration and remember which campaign brought you here. We do not record sessions. You can decline and still use the site. Privacy details.