Monitoring the System - Teradata Database

Teradata Database Administration

Teradata Database
Release Number
English (United States)
Last Update
Product Category

Measuring System Conditions

The following table summarizes recommended system conditions to measure.


System Conditions

What to Use

What to Collect

How to Use

Response time

Heartbeat queries

  • Response-time samples
  • System-level information
  • Saved samples can be used to:

  • Track trends
  • Monitor and alert
  • Validate Priority Scheduler configuration
  • Baseline testing

  • Response-time samples
  • Execution plans
  • Check for differences +/- in response time.
  • Check EXPLAINs if degradation is present.
  • Collect / keep information for comparison when there are changes to the system.
  • Database Query Log (DBQL)

    Application response time patterns

    Track trends:

  • To identify anomalies
  • To identify performance-tuning opportunities
  • For capacity planning
  • Resource utilization

    Resource Usage

  • ResNode Macro set
  • SPMA summarized to one row per node
  • Look for:

  • Peaks
  • Skewing, balance
  • AMPUsage

    CPU seconds and I/O for each unique account

    Use this to quantify heavy users.


    CPU, I/O, spool used, rows returned


    Data growth

  • Script row counts
  • Permspace
  • Summary row per table once a month

    Look at trends.

    Changes in data access


    Summary row per table and the number of accesses once a month

    Look for increases in access, trends.

    Increase in the number of active sessions

    LogOnOffV, acctg

    Monthly and summarized number of sessions

    Look for increases in concurrency and active users.

    Increase in system demand




    Query counts and response times, plus other query information

    Look for trends, including growth trends, and measure against goals.

    Resource Usage

    System demand



    Queries with errors or queries that have been canceled