Boosting Teradata Statistics Performance with New Syntax in Release 14.00

Release 14.00 introduces significant enhancements for Teradata statistics, which merit a detailed explanation.

Familiarizing yourself with the new syntax is crucial, as it is now the standard. This article will delve into the benefits of the updated syntax, which is accessible with Teradata 14.00.

COLLECT STATISTICS COLUMN (A), COLUMN(B), …, COLUMN(Z) ON TABLE_NAME;

The new syntax allows for grouping multiple collect statistics requests for a single table into a single request. While the old syntax remains an option, it is not advised due to the notable enhancements in performance and resource utilization.

When utilizing the new syntax to group statistics collections on columns, the Teradata optimizer strives to optimize your request in order to minimize table scans. For instance:

COLLECT STATISTICS COLUMN(A,B), COLUMN(A), COLUMN(B);

In the example, the optimizer requires a single table scan to generate statistics for column A, column B, and columns (A, B). Technically, the statistics for (A, B) are initially computed, and subsequently, the spool created during this computation is reused to calculate the statistics for A and B.

While this method may not always be used, it can lead to significant enhancements in performance and resource utilization. It is important to note that utilizing the old syntax would result in three table scans. This performance and resource usage improvement can be perceived upon implementation or after the second refresh of the relevant statistics.

Conclusion:

Rewriting your current statistical statements in the new syntax is highly recommended.

Related Services

⚡ Need Help Optimizing Your Data Platform?

We cut data platform costs by 30–60% without hardware changes. 25+ years of hands-on tuning experience.

Explore Our Services →

📋 Considering a Move From Teradata?

Get a personalized migration roadmap in 2 minutes. We have migrated billions of rows from Teradata to Snowflake, Databricks, and more.

Free Migration Assessment →

📊 Data Platform Migration Survey

Help us map where the industry is heading. Results are public — see what others chose.

1. What is your current data platform?

2. Where are you migrating to (or evaluating)?

Migrating FROM
Migrating TO

Thanks for voting! Share this with your network.

Follow me on LinkedIn for daily insights on data warehousing and platform migrations.

Stay Ahead in Data Warehousing

Get expert insights on Teradata, Snowflake, BigQuery, Databricks, Microsoft Fabric, and modern data architecture — delivered to your inbox.

2 thoughts on “Boosting Teradata Statistics Performance with New Syntax in Release 14.00”

  1. In previous versions, each collect statement required a separate full table scan, but synchronized scanning was always possible (i.e. using a common spool for building the statistics) by issuing the statements in parallel:

    COLLECT STATISTICS COLUMN(A);
    COLLECT STATISTICS COLUMN(B);
    COLLECT STATISTICS COLUMN(A,B);

    Reply
  2. Thank you for your explanation.
    as you said the example for collect statistics new syntax :
    COLLECT STATISTICS COLUMN(A,B), COLUMN(A), COLUMN(B);

    how it would be in Old Syntax and how the optimizer will work for Old Syntax.

    Reply

Leave a Comment

DWHPro

Expert network for enterprise data platforms. Senior consultants, project teams built for your challenge — across Teradata, Snowflake, Databricks, and more.

📍Vienna, Austria & Jacksonville, Florida

Quick Links
Services Team Teradata Book Blog Contact Us
Connect
LinkedIn → [email protected]
Newsletter

Join 4,000+ data professionals.
Weekly insights on Teradata, Snowflake & data architecture.