The provider wraps the official Teradata Database driver; you can connect to the Lyftrondata Provider for Teradata using the same connection properties and access the same functionality as the underlying Teradata driver. You also need to install the official driver alongside the Lyftrondata Provider for Teradata.
Connecting to Teradata
To connect to Teradata, provide the following authentication information and specify the database server name.
- User; Set this to the user name of a Teradata user.
- Password: Set this to the password of the Teradata user.
- DataSource: Specify the Teradata server name, DBC Name, or TDPID.
- Port: Specify the port the server is running on.
- Database: Specify the database name. If not specified, the provider connects to the default database.
Enable DataEncryption to encrypt connections with TLS/SSL.
Connecting Through a Firewall or Proxy
Set the following properties:
- To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
- To tunnel the connection, set FirewallType to TUNNEL.
- To authenticate, specify FirewallUser and FirewallPassword.
- To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.
Troubleshooting the Connection
To show provider activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.
- Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
- Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.