Unity Director handles data for mission critical applications that demand continuous high availability (HA), data location identification, session management, and data synchronization. It simplifies multiple Teradata Database system management tasks including routing users to the data location, rerouting users during an outage, and synchronizing database changes across Teradata Database systems. Unity Director integrates with Unity Ecosystem Manager to enable administrators to view system and table health, receive warning and critical alerts, and view analytics and statistics about data operations. As a bulk load option, Unity Director can utilize Unity Loader to selectively route large data loads from a client to Teradata systems without additional administrator operations.
In this article, I will be showing you how to establish Unity Director 14.00 routing rules which will enable you to efficiently load balance reports across multiple managed Teradata systems.
A routing rule defined in Unity Director is used along with user mappings to enable administrators to efficiently manage client connections and route them to the desired Teradata managed system(s). You can define read-only or read/write routing rules. I will demonstrate how to build create preferred routing rules via Unity Director’s graphical user interface and command line utility.
When MicroStrategy reporting utilizes temp table creation capabilities Unity 13.10 was required to send .ddl and write requests to all managed Teradata systems. This resulted in resources being consumed on both systems. In Unity Director 14.00, create preferred routing rules were added to specifically reduce resource consumption. Now when temporary tables are needed the Unity Administrator can establish create preferred routing rules and user mappings that will direct the .ddl and read/writes to go to one system. In the below video you will see this capability.