Connect to a Teradata instance

Important: when reverse-engineering or forward-engineering a Teradata instance, the (Teradata) user used to connect to the target instance should have access to read SYSUDTLIB system database to retrieve DDL scripts for UDT, UDM etc...

 

More information is available here.

 

The Teradata instance can be hosted on-premises, or on virtualized machines in a private or public cloud.  

 

Teradata supports 2 authentication mechanisms: basic auth, or LDAP.  Hackolade Studio does not currently support LDAP -- only basic auth.  To be sure of the auth mechanism for your username, and if they are able to connect via "sql connect tool", you can check the mechanism using the following query:

SELECT Username, LDAP, MechanismName
FROM dbc.SessionInfoV
WHERE Username = USER;

 

In "MechanismName" there should be either:

• TD2 for basic auth
• LDAP (or any other) for LDAP mechanism respectively

 

 

In the Hackolade connection settings dialog, give a meaningful name to the connection, then set the the host and port if you wish to limit the scope of the discovery.

 

 

Important: when reverse-engineering or forward-engineering a Teradata instance, Hackolade is leveraging the Teradata Java client.  You will need a working and properly configured Java environment (minimum Java 11).  Hackolade tries to autodetect JAVA_HOME on your system but you can still configure it manually if your installation is specific (or if our automatic detection can’t find JAVA_HOME).

 

 

If required, you may enter your username and password