More and more often, I experience in projects that Teradata is used as a database for tactical workload or OLTP applications. I can only warn against designing the corresponding databases without much thought. Teradata is an excellent database for strategic data warehousing. Most of the time, you get high-performance queries without applying any special design

Read More

In a normalized PDM, relation tables are often difficult to query. We have to choose precisely one Primary Index as a query path for direct accesses. The other side of the relationship typically needs a full table scan. Using a Teradata join index can help improve the performance of queries. Below is an example table.

Read More

How to use the Teradata MAPS Architecture? In an earlier article (link to All Rows on One AMP – By Design), I showed an alternative design for small reference tables, ensuring that all rows in the table are stored on a single Teradata AMP using the Teradata MAPS architecture. The design allows for single-AMP retrieval

Read More

What is the Teradata Primary Index? The Teradata primary index is a mechanism that decides where each data row is physically located. It may be based on a single column or multiple columns. The values of the primary index columns may be unique or non-unique. Don’t confuse the primary index with the primary key of

Read More

Quick Navigation 1. Complete and up-to-date Statistics2. Teradata Primary Index Choice3. Teradata SQL Tuning with Indexing & Partitioning4. Query Rewriting5. Teradata SQL Tuning with Real-Time Monitoring6. Comparison of Resource Usage 1. Complete and up-to-date Statistics Teradata SQL Tuning begins by providing the optimizer with the statistics it needs. This must always be done as a

Read More

The primary goal is to show you how the number of rows per base table data block impacts the selectivity. The example we are using will show you exactly how Teradata NUSI selectivity is related to the average data block size,  the average row size, and the number of rows per data block. First, we

Read More

The Essential Facts About NOPI Tables in Teradata Teradata NOPI Table Limitations No SET tables allowed No Identity columns allowed No Row-Level Partitioning allowed No UPDATE, MERGE INTO, or UPSERT allowed No Permanent Journaling possible Can’t be defined as Queue Tables No UPDATE triggers allowed No Hash Index allowed No Multiload, as its load algorithm

Read More

Teradata ALTER Table versus INSERT INTO Changing the structure of a Teradata table can require a lot of resources for large tables. In principle, two methods are available. We can modify the DDL using a Teradata ALTER TABLE or create an empty table with the desired DDL statement and copy the data using the Teradata

Read More

The initial situation without any index In this blog post, I will show you how you can optimize a query step by step using the right tools that Teradata offers you. Let’s start with the following test scenario: CREATE TABLE Orders ( OrderId BIGINT NOT NULL, CustomerId BIGINT NOT NULL, Amount BIGINT ) PRIMARY INDEX

Read More

How Advanced Is The Teradata Columnar Solution? A Column Store is basically characterized by 3 properties: Improved compression compared to Row Stores. This results from the fact that considerably better compression rates can be achieved by packing columns into data blocks. Since the values of a column come from a domain, the entropy is much

Read More