322 technical articles on Teradata, Snowflake, Databricks, SQL tuning and data warehouse architecture — written from production experience, not vendor decks.
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. Change history tables are typically complex. …
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 …
Introduction Teradata offers several methods for conducting joins, but all necessitate one prerequisite. The paired table rows must reside on identical AMPs. The chosen method for joining and relocating data is called a join strategy. The preparation for each join method varies. The choice of Teradata join strategy utilized by the Optimizer is determined by …
The Art of Teradata Performance Tuning As a Teradata Performance Tuner, technical expertise and experience are essential, occasionally accompanied by fortuitous circumstances. I’ll demonstrate the remarkable outcomes that can be attained by rephrasing a query using this example. Assuming this scenario: One table has a minimal number of rows, while the other is partitioned and …
A recent question came in about how the Teradata Optimizer uses multi-column statistics. Here are the essential details: The Optimizer uses multi-column statistics when the query’s WHERE clause covers all columns. This example pertains to Teradata 13.10. The query was executed without gathering Primary Index statistics, resulting in low confidence from the Optimizer. To boost …
Here is an illustration depicting the design of real-world map-reduce implementations, such as Hadoop: How the Components Fit Together The input files reside in a distributed file system, such as HDFS for Hadoop, or GFS as Google calls it. Worker processes handle mapper or reducer tasks. Mappers read data from HDFS, apply the mapping function, …
Learn about the differences between GROUP BY and DISTINCT for aggregations in Teradata. The optimizer now selects the appropriate algorithm depending on data demographics. Understand when to use each method to optimize query performance.
Learn about locking in Teradata to ensure data integrity and consistency. Teradata automatically selects the best lock for each situation to prevent data inconsistencies.
Learn about the goals of SQL tuning and how to optimize database performance by reducing resource usage. Skew, IOs, and CPU seconds are key metrics. Discover how to ensure completeness and correctness of Teradata statistics, detect missing and stale statistics, and improve query plans.
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.