Introduction to Teradata Performance and NOT NULL Welcome to our latest Teradata performance blog post, a series designed to provide valuable insights into SQL queries. This article spotlights ‘NOT IN’. To delve deeper into ‘NOT IN’, it is crucial to comprehend a frequently neglected SQL database design principle: properly defining columns that cannot hold NULL …
Learn how to overcome the hurdle of using Teradata Identity columns with Volatile Tables. Discover a workaround using the ‘CREATE TABLE AS’ statement.
Teradata Statistics Histograms – A Short Introduction Many are familiar with 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 to …
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 …
Learn about locking in Teradata to ensure data integrity and consistency. Teradata automatically selects the best lock for each situation to prevent data inconsistencies.
What are Deadlocks in Teradata? Deadlocks arise when two transactions hold locks on database objects required by the other transaction. Here is an example of a deadlock: Transaction 1 locks some rows in Table 1, and transaction 2 locks some rows in Table 2. The next step of transaction 1 is to lock rows in table 2, and …
Teradata MERGE INTO vs. UPDATE This article compares the UPDATE statement to the MERGE INTO statement, analyzing their respective performance differences and limitations. The Teradata MERGE INTO statement positively impacts performance by reducing I/O operations due to certain properties related to its performance. MERGE INTO offers an advantage in lower IOs as Teradata processes each …
A normalized data model can increase the complexity of creating performant queries due to the higher number of tables that must be linked compared to a denormalized data model. It is essential to select a primary index precisely to optimize queries and joins, enabling them to have a direct access path. However, relationship tables often …
Teradata employs two distinct approaches in Ordered Analytic Function for preparing data geography necessary for processing. This article elucidates both approaches and their respective merits and demerits. Teradata Ordered Analytical Functions Teradata Analytic Functions are versatile tools that allow for a range of applications. The capability to retrieve previous and subsequent rows is critical in …
Expert network for enterprise data platforms. Senior consultants, project teams built for your challenge — across Teradata, Snowflake, Databricks, and more.
📍Vienna, Austria & Miami, Florida
Join 4,000+ data professionals.
Weekly insights on Teradata, Snowflake & data architecture.