Teradata Heartbeat

A heartbeat query can be any SQL statement run at specific intervals whose response time isbeing monitored.

  • Measure response time as an indicator of system demand or system/database hangs
  • Initiate an alert system if response time degrades so that you can take appropriate action

Heartbeat queries are classified as

  • System
  • Production

System Heartbeat Queries:

  • Used to check overall system/database hangs, to react when response time reaches a certain thresholds, or when stalled, such as send alert and/or capture system level information
  • It should execute diagnostics that capture the state of the system if performance stalls
  • They are intended to focus on Teradata core system. They should be short running , low impact queries on tables that are normally not write locked
  • They are more useful when run frequently (for example 5-10 mins)
  • They should be run on system nodes (which eliminates other factors like middle tiers, network connections)

Example of system heartbeat query:

select * from dbc.dbcinfo;

As the query runs, Teradata Manager can monitor the query, logging start and end times.

Production Heartbeat Queries:

  • Response times play a major role in the production heartbeat queries, these need to be monitored and stored for tracking purposes
  • Response time are an indicator of system demand. When system demand is high, heartbeat response is high
  • They can be run on production user tables
  • Monitor overall response
  • Monitor specific area of the job mix
  • Can be more complex and similar in nature to a particular type of production query, running in the same Priority Scheduler performance group
  • They are run less frequently (for example 20-60 mins)
Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *