Managed Routing Session Considerations | Teradata Unity - Managed Routing Session Considerations - Teradata Unity

Teradata® Unity™ User Guide

Product
Teradata Unity
Release Number
16.50
Published
January 2020
Language
English (United States)
Last Update
2020-02-04
dita:mapPath
frp1571162435023.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2520
lifecycle
previous
Product Category
Analytical Ecosystem
For managed routing sessions, do the following:
  • Enable Proxy authentication with Teradata Database 14.10 or later. This is not required for passive routing if using TD2 authentication.
  • Use NTP to synchronize all time zones. All systems act as one logical system.
  • Do not change DBQL and related configuration settings with Unity in managed sessions. Run those changes directly on each managed Teradata system.
For managed routing sessions, the following options are not supported:
  • XQuery
  • Teradata (QueryGrid) Foreign Server, including Foreign Server definitions and Foreign Server access within SQL code.
  • SQL-H
  • Writes that read from system-specific information.
    Writes are supported in passive routing, but are not synchronized. CDM does not synchronize writes from the user DBC.
  • Usernames and database objects containing periods, single quotation marks, spaces, or special characters as managed objects
In managed sessions, DDL requests using ETL routing may not achieve expected performance. When processing multiple, simultaneous requests, use Passive routing.