Connect to a Teradata instance

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

Our reverse-engineering process requires at least read-only privileges for the following tables:

• Databases/Schemas: SELECT on DBC.DatabasesV
• Tables/Views: SELECT on DBC.TablesV
• Columns: SELECT on DBC.ColumnsV
• Check Constraints: SELECT on DBC.CheckConstraintsV
• Unique Constraints: SELECT on DBC.UniqueConstraintsV
• Foreign Keys: SELECT on DBC.All_RI_ParentsV
• Indexes: SELECT on DBC.IndicesV
• Views: SELECT on DBC.TablesV.ViewText

The following must be granted explicitly for each table in the instance, or the user must be an owner of the table

• UDTs: SELECT on SYSUDTLIB
• Table DDL: SHOW TABLE on <db>.<table>
• For sampling data: SELECT TOP 1 on <db>.<table>

For reference:

• Query to check the actual user rights (update the UserName):

SELECT DatabaseName, TableName, AccessRight FROM DBC.AllRights WHERE UserName='demo_user' ORDER BY 2, 1;

• To grant a privilege please review instructions in this page

If you want to apply to instance, you will of course need write rights for the above.

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.

If required, you may enter your username and password