Unity Director 14.00 and Unity Loader 14.00 are now available! Last year Teradata announced a new query management and data synchronization product to the marketplace. Now we've taken it to the next level. Unity Director 14.00 provides a new user interface, new and improved routing rules and scalable configuration options. Unity Loader 14.00 is a new offering extending beyond the basic synchronization of SQL updates and now enabling the intelligent synchronization of high volume/bulk loads.
Leveraging Teradata's patented SQL Multicast technology, Unity Director and Unity Loader continue to change the paradigm of query management and data synchronization across multiple Teradata systems. Here are a few highlights of the 14.00 releases.
Unity Director is focused on query management and SQL-based data synchronization across multiple Teradata systems. For query management, Unity Director enables not just query failover but also intelligent query routing based on the SQL object being accessed. Users can choose from several routing modes: Named, Preferred, or Auto Routing. Director 14.00 now provides the ability to designate a given system for specific CREATE operations, allowing for greater control of certain workloads - great for in-database transformations or BI tools that leverage temporary tables. Unity Director 14.00 also made some significant improvements with respect to authentication, now supporting LDAP, Kerberos and SPNEGO authentication protocols.
Unity Director 14.00 provides greater scalability as well. Not only does it support a greater number of database objects and concurrent sessions, but it also introduces a new Teradata Managed Server for increased recovery log space for both SQL-based and Bulk Load (Unity Loader) operations. The new Teradata Managed Sever itself provides new levels of scalability in that customers can now configure multiple servers in a single data center based on their data synchronization and load volume requirements.
Finally, Unity Director 14.00 introduces a brand new user interface. To be more consistent with other applications in the Teradata Analytical Ecosystem, Unity Director has replaced its original UI with a Viewpoint portlet. The new user interface allows for greater flexibility when configuring systems under Director control and defining specific routing rules.
In the past, synchronizing large volumes/bulk data to two or more Teradata systems required a custom-built dual-load engagement. With the introduction of Unity Loader 14.00, custom dual-load solutions are no longer needed. Unity Loader is a powerful offering providing intelligent and selective routing of bulk loads to the appropriate Teradata system.
For more information on Unity Director 14.00 and Unity Loader 14.00, follow the links below.
After reading you article I have the following questions:
1) Will Unity Director/Loader require a new or upgraded TMS Server if Customers are using TMS Servers with 13.10?
2) Regarding data-syncronization and TPT Bulk Loading - If we have TD-system-A and TD-System-B and:
- we buk load data, If TD-system-A already has the table will it perform UPSERTS and if TD-system-B does not have the table will it be created and perform INSERTS? IF yes, how would it handle post syncronization validations?
does Unity Loader support FICON (Channel) connections ? If not are there any plans to add support for this ?
Andrew - Unity Loader does not support FICON channel connections today. Our plan is to support mainframe in the futrue, yet there is no committed date for this functionality.
Sorry for the delay in response.
1) Unity Director/Loader 14.00 will only require a new managed server if Unity Loader is purchased. If you are only using Unity Director 14.00, no new mananged server is need, the Director 13.10 server is sufficient. Since Loader manages the bulk load operations, a much more powerful managed server is needed with additional disc capacity. Summary: when purchaseing Loader 14.00, a new managed server is required.
2) The SQL Multicast function of Director/Loader works slightly differently than you described. When doing a TPT Load through Director/Loader, we will apply the load to where ever the affected SQL Object exists. So if the table only exists on System A, we will apply the load only to system A. The Director Data Dictionary keeps track of what tables exist in each system. If desired, you could use Unity Data Mover (different product) to perform a one-time table copy to system B, put that table on system B under Director control, and then Director would apply any future INSERTS to that table to both systems.
Hope this helps.
I heard about Unity Director, Unity Loader products in Ecosystem. But is there any element known as Unity Data Mover(DM). I know Data Mover and its functionality. We are implementing the HA solution over here, i heard the word Unity Data Mover. I am not sure whether there is a seperate product knwn as Unity DM or it is same as DM.
Appreciate your comments on this.
Geeta - "Unity Data Mover" is the new name for what was formerly known as "Teradata Data Mover". (same product, new name) This was part of a rebranding effort to group certain products under the Teradata Unity Portfolio of products.
I think TD did not publish any manual on Teradata Unity Loader User Guide or Configuration guide. Am i correct?
Unity Loader requires Unity Director. For this reason, all Unity Loader documentation is in the Unity Director User Guide. Here is the link: