Multiple QGM Cluster Considerations | Teradata QueryGrid - Multiple QueryGrid Manager Cluster Considerations - Teradata QueryGrid

QueryGridâ„¢ Installation and User Guide - 3.06

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata QueryGrid
Release Number
3.06
Published
December 2024
ft:locale
en-US
ft:lastEdition
2024-12-07
dita:mapPath
ndp1726122159943.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
Product Category
Analytical Ecosystem

For two data source systems to connect through QueryGrid, both systems must be registered to the same QueryGrid Manager cluster. As of QueryGrid 02.11, data source systems can belong to up to three QueryGrid Manager clusters.

Use Case: Production and Development

One of the main reasons for maintaining multiple clusters is to maintain a development cluster separate from a production cluster. A production or development data source can be part of both the production and development cluster. This allows the development system to be seeded with data from production while still maintaining separate environments.

Use Case: Full Vantage Cluster and External Ecosystem

Another reason for having multiple clusters is to keep the internal Full Vantage cluster isolated from the ecosystem deployment of QueryGrid while still allowing Analytics Database to belong to both the Vantage internal cluster and the external ecosystem cluster.