Teradata
A collection of 307 issues
Teradata SQL Tuning: How Query Rewriting Can Reduce Runtime from 40 Minutes to Seconds
Teradata vs. Redshift: A Comparison of Join Strategies and Architecture
High-Performance Calculations with Teradata Ordered Analytical Functions
Understanding Teradata Join Estimation: Heuristics and Importance of Statistics Collection
What is Teradata Join Estimation?
This article demonstrates the functioning of Teradata Join Estimation in the absence of statistics. It presents the heuristics employed to estimate row count and emphasizes the importance of collecting statistics on all join columns.
Teradata Join Estimation Heuristics
The worst-case scenario involves joining two tables
Detecting Overlapping Time Periods with Teradata OVERLAPS Command: A Simple Syntax Guide
Learn how to use the Teradata OVERLAPS command to detect overlapping time periods with this example query. Caution: minimum overlap required.
Optimizing Teradata Statements Containing Multiple JOINS
Optimizing Queries with LIKE Operator in Teradata
Learn how to optimize LIKE operator queries in Teradata to avoid full table scans and improve performance. Read on for expert tips and tricks.
Teradata Columnar Compression Methods: Run-Length, Dictionary, and Delta Compression
Learn about the benefits of compression in Teradata Columnar, including a reduction in permanent space and disk IOs. Different compression methods are used, including run-length, dictionary, and delta compression. This article explains how each method works and the advantages of using them.
Designing Small Reference Tables for Teradata: Storing All Rows on One AMP for More Efficient Queries
When designing tables for Teradata, it is important to distribute the rows across all AMPs in the system evenly. For instance, on a 100-AMP system with 100,000 rows, the objective would be to allocate roughly 1,000 rows per AMP.
I agree with the design guideline for many tables