Dynamic Routing Rule Changes Using Query Band Requests | Teradata Unity - Dynamic Routing Rule Changes Using Query Band Requests - Teradata Unity

Teradata® Unity™ User Guide

Product
Teradata Unity
Release Number
16.51
Published
May 2020
Language
English (United States)
Last Update
2020-06-01
dita:mapPath
oic1588030762460.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2520
lifecycle
previous
Product Category
Analytical Ecosystem

You can use a query band statement to change a sessions routing rule dynamically. The query band rule makes sure that particular reporting or load processes use a specific routing rule.

If the client application is already using the routing rule, then the query band has no effect. If the client specifies a routing rule different from the currently used, it disconnects its Unity sessions and reconnects using the specified routing rule.

The example below demonstrates a report that is intended to run only on the first DB1 system, using the DB1_Only routing rule.
SET QUERY_BAND = 'UNITYROUTING=DB1_Only;’ For Session;