Change Configuration | Teradata QueryGrid - Active, Pending, and Previous Teradata QueryGrid Configurations - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide

Teradata QueryGrid
Release Number
July 2022
English (United States)
Last Update
Product Category
Analytical Ecosystem
Making changes to a Teradata QueryGrid configuration can potentially impact production workloads. Configuration changes include changes to the following:
  • Fabric, connector, and node software package versions
  • Fabric configuration
  • Connector configuration
  • Links and link pairings
  • Networks, communication policies, and user mappings associated with a link

The fabric, connector, and software packages have versions, and each of the components listed above has a version in a Teradata QueryGrid configuration. Each component in a Teradata QueryGrid configuration can have one of the following states. These states allow you to manage changes to your Teradata QueryGrid configuration.

Since fabric processes bind to a port, three separate ports (such as, 5000, 5001, and 5002) are needed to run active, pending, and previous fabrics all at the same time.

Item Description
Active The configuration actively processing production workloads in the production environment. The configuration has been tested and verified.

If you replace an active version, the formerly active version becomes the previous version and the former previous version is deleted.

Pending A new or modified configuration that has been pushed to the production environment for testing (without affecting production workloads).

If you activate a pending version, the formerly active version that you replaced becomes the previous version.

Previous A previous configuration in the production environment.

If you activate a previous version, the active version becomes the previous version, and any pending version remains the pending version.

For more information, see Working with Active, Pending, or Previous Versions.