ODBC Driver Setup Parameters - ODBC Driver for Teradata

See the “data-source-name=<driver>” option in ODBC Data Sources Section.

This is a comment field that is not retrievable by an SQL or ODBC command.

See the “Description=<data-source-desc>” option in Data Source Specification Section.

• Enter the database system name (alias or FQDN) without COP suffix.
• Enter the name or IP address of the LAN-connected node in your system, one per line.

After providing the name, ODBC Driver for Teradata dynamically detects all associated COP entries.

You must define COP names or the name without COP suffix in either a Domain Name Services (DNS) or the local hosts file. For more information, see Cop Discovery.

Clear this check box to enable the user to connect to the database using Conventional Sign On (CSO).

Select this check box to enable the user to connect to the database using Single Sign-On (SSO).

In CSO from a network client, the user must provide a database username and password. These are sent to the database for validation. If the username exists and the password correctly matches, access is allowed. Otherwise, the connection request is rejected.

In SSO, the username and password are not submitted. The database username is derived from the user identity on the client platform.

Click Test, enter the Authentication Parameter or Password, and click OK to test the connection.

If the DSN entry does not have enough information to make the connection, Connection Dialog appears. See Completing Connection Information for more information.

Enter the password required for the default Username.

Instead of storing the actual password in DSN, Teradata recommends using a Teradata Wallet reference string as a password. Password and Teradata Wallet String fields are mutually exclusive, so a DSN can have either the Password or a Teradata Wallet String.

For more information, see Teradata Wallet.

See complete descriptions at Authentication Mechanisms.

Indicate a string of characters to be regarded as a parameter of the authentication mechanism. The string is transparent to ODBC Driver for Teradata and is passed to the Teradata authentication software called to set the mechanism.

Enclose characters [] {} () , ; ? * = ! @ in braces.

The value may be enclosed by $tdwallet(), for example, $tdwallet(WalletRefString). If it is not, the driver will automatically enclose it when the value is saved.

For more information, see Teradata Wallet.

Specify a username for the default database.

Shows the default username that was specified during the data sources configuration of the driver. The default value can be overridden here. If required, the user is prompted for additional information. The username and password are Teradata-specific, not to be confused with Windows user ids and passwords.

The username is interpreted in the context of the authentication mechanism. If, for example, the authentication mechanism is NTLM, then the username is assumed to be a Windows username.

If the authentication mechanism allows fully qualified usernames, then the username can contain a domain or realm; for example, {judy@linedata}. Values containing a character such as @ must be enclosed in braces.

SSO is indicated by the absence of a Username and Password.

See the “Username=<name>” option in Data Source Specification Section.

The value may be enclosed by $tdwallet(), for example, $tdwallet(WalletRefString). If it is not, the driver will automatically enclose it when the value is saved.

For more information, see Teradata Wallet.

Specify a default database.

See the “DefaultDatabase=<database-name>” option in Data Source Specification Section.

Enter a user in the database while configuring the data source rather than having to provide account information during configuration of ODBC Driver for Teradata.

This information can be used to help isolate users, to find out what application the users are running, or to restrict users from logging on.

See the “AccountStr=<account>” option in Teradata DSN Options.