Connections > Teradata connection properties > Connect to Teradata
  

Connect to Teradata

Let's configure the Teradata connection properties to connect to Teradata.

Before you begin

Before you get started, be sure to complete the prerequisites.
Check out Prerequisites to learn more about the authentication prerequisites and tasks that you must perform.

Connection details

The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Type
Teradata
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
For information about how to configure and use a secrets manager, see Secrets manager configuration.
Runtime Environment
The name of the runtime environment where you want to run tasks.
Specify a Secure Agent.
TDPID
The name or IP address of the Teradata database machine.
Database Name
The Teradata database name.
If you do not enter a database name, Teradata PT API uses the default login database name.
Code Page
Code page associated with the Teradata database.
Select one of the following code pages:
  • - MS Windows Latin 1. Select for ISO 8859-1 Western European data.
  • - UTF-8. Select for Unicode and non-Unicode data.
When you run a task that extracts data from a Teradata source, the code page of the Teradata PT API connection must be the same as the code page of the Teradata source.

Authentication types

You can configure the Native, LDAP, or KRB5 authentication type to connect to the Teradata database.
Select the required authentication type and then configure the authentication-specific parameters.
Note: Data Ingestion and Replication does not support the KRB5 and LDAP authentication types.

Advanced settings

The following table describes the advanced connection properties:
Property
Description
Tenacity
Amount of time, in hours, that the Teradata PT API continues attempting to log in again when the maximum number of operations runs on the Teradata database.
Specify a positive integer.
Default is 4.
Max Sessions
Maximum number of sessions allowed for the Teradata PT API to establish connection with the Teradata database.
Specify a positive, non-zero integer. Default is 4.
Min Sessions
Minimum number of Teradata PT API sessions required for the Teradata PT API job to continue.
Specify a positive integer between 1 and the value specified in the Max Sessions field.
Default is 1.
Sleep
Amount of time, in minutes, that the Teradata PT API waits before it attempts to log in again when the maximum number of operations run on the Teradata database.
Specify a positive, non-zero integer.
Default is 6.
Data Encryption
Enables full security encryption of SQL requests, responses, and data.
Default is disabled.
Block Size
Maximum block size, in bytes.
Teradata PT API uses this property to read the data block size from source through the Export operator.
Maximum is 16775168 bytes for Teradata database version 16.20 and later.
If the Teradata database version is earlier than 16.20, Teradata scales down the block size from 16775168 bytes to the maximum allowed value. The block size 16775168 is not allowed in the Spool mode.
For more information, see the Teradata logs and verify the Teradata documentation of the same version.
Metadata Advanced Connection Properties
The optional properties for the JDBC driver to fetch the metadata from Teradata.
For example, tmode=ANSI.
Enable Metadata Quotification
Determines if a Teradata connection reads reserved words used in table or column names from the Teradata database.
Select the Enable Metadata Quotification checkbox for the Secure Agent to read reserved words from Teradata.