Architecture
A collection of 111 issues
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.
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
Teradata Statistics Design for High Performance: An Introduction
Learn how Teradata 14.10 simplifies statistics collection for better performance. Discover new features that identify unused and missing statistics.
VantageCloud Lake: Turbocharge Your Data Warehousing with Teradata's Innovative Solution
Teradata: Unleashing the Potential of a Powerful Data Warehouse Solution
Introduction
Discover the world of Teradata, an industry-leading data warehouse and analytics platform that offers unparalleled performance, scalability, and ease of use. This comprehensive blog post will explore Teradata's key features and benefits, learn about its architecture, and discuss its significance in modern data-driven organizations.
Stay tuned as
Enhancing Your Teradata Vantage Design with Teradata Historisation: A Comprehensive Method
Situation and Setup of a Historisation in Teradata Vantage
Imagine that the time has come to improve your physical data model. Flawed or obsolete Teradata Vantage historisation design decisions need to be corrected. You are asked to separate tables of the same entity with different attributes. We do not question