16.10 - Managed Sessions Considerations - Teradata Unity

Teradata Unity User Guide

Teradata Unity
Release Number
January 2018
English (United States)
Last Update
Proxy authentication must be enabled with Teradata 14.10 or later. This is not required for passive routing if using TD2 authentication.
Since all systems act as one logical system, time zones on the Teradata systems and Unity servers must be identical. Use NTP to synchronize.
Do not change DBQL and related configuration settings via Unity in managed sessions. Instead, you can execute those changes directly on each managed Teradata system.
For managed sessions, the following are not supported:
  • XML and JSON data types
  • XQuery
  • Teradata (QueryGrid) Foreign Server, including Foreign Server definitions and Foreign Server access within SQL code.
  • SQL-H
  • UDMs, preventing most uses of GEOSPATIAL data types
  • Table operators
  • Writes that read from system-specific information.
    These write are supported in PASSIVE routing but will not be synchronized. CDM will 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.