When you connect to Teradata through the Arrow Flight SQL Connector (SERVER execution type):
- The connected Teradata Database uses a JDBC connection to validate your credentials
- To reduce authentication overhead and improve performance, the connector uses a JDBC connection pool
- If a valid pooled connection already exists for your credentials, the connector reuses that connection instead of opening a new JDBC connection
- If no valid pooled connection is available, the connector establishes a new JDBC connection to authenticate your request
This approach improves connection efficiency while the Teradata Database validates your credentials.
Teradata Database Connection Settings
Use these settings to identify the Teradata Database that Teradata Fabric connects to when using the SERVER execution type.
| Setting | Description |
|---|---|
| Teradata Advanced SQL Engine | Specifies the IP or hostname of the Teradata Database. Required for SERVER execution type |
| Teradata Advanced SQL Engine Port | Specifies the port of the Teradata Database. Required for SERVER execution type. |