x

You can configure the adapter from either the Web Console or the Data Management Console.

1. From the Web Console menu bar, click Adapters

   or

   from the Data Management Console, expand the Adapters folder.

   The Adapters folder opens.

2. Expand the Available folder, if it is not already expanded.
3. Expand the appropriate group folder and the specific adapter folder. The group folder is described in the connection attributes reference.
4. Right-click the adapter name/version and select Configure.

   The Add Adapter to Configuration pane opens.

5. Enter values for the parameters required by the adapter as described in the connecton attributes reference.
6. Click Configure. The configured adapter is added to the Adapters list in the navigation pane.

x

The Teradata adapter is under the SQL group folder.

This chart describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.

Note that the release numbers on the Web Console for DBMS Add and DBMS Change panes refer to the Teradata ODBC driver, not the Teradata DBMS release.

Attribute	Description
xConnection Name	For the ODBC interface only, this is the logical name used to identify this particular set of connection attributes.
x xDatasource or Server	Valid Teradata data source name (DSN). There is no default DSN; you must enter a value. For the ODBC interface, this DSN name should match the entry in the $HOME/.odbc.ini. file. For the CLI interface, this field is labeled SERVER and requires a valid Teradata TDP value. On Windows and UNIX this is the value of i_dbcpath in the clispb.dat file. Refer to the Teradata Utilities documentation for details.
xSecurity	There are two methods by which a user can be authenticated when connecting to an Teradata database server: Explicit. The user ID and password are explicitly specified for each connection and passed to Teradata, at connection time, for authentication. Password Passthru. The user ID and password received from the client application are passed to Teradata, at connection time, for authentication.
xUser	Authorization by which the user is known to Teradata.
xPassword	Password associated with the authorization ID.
xSelect profile	Select a profile from the drop-down list to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default. If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down list and enter a name in the Profile Name input box (The extension is added automatically).

x

ENGINE SQLDBC SET CONNECTION_ATTRIBUTES {connection DSN_name|Server} 
/userid,password

where:

SQLDBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

connection

For the Adapter for Teradata ODBC, this is the logical name used to identify this particular set of connection attributes.

Note that one blank space is required between connection and DSN_name.

DSN_name

For the Adapter for Teradata ODBC, this is the Teradata Data Source Name (DSN) you wish to access. It must match an entry in the odbc.ini file.

Server

For the Adapter for Teradata CLI, this is the Teradata Director Program number (TDPn), where n is the number. This is the value of i_dbcpath in the clispb.dat file.

userid

Is the primary authorization ID by which you are known to Teradata.

password

Is the password associated with the primary authorization ID.

Top of page

Example: Declaring Connection Attributes

The following SET CONNECTION_ATTRIBUTES command connects to the Teradata database server named SAMPLESERVER with an explicit user ID (MYUSER) and password (PASS). To ensure security, specify connection attributes from the Web Console, which encrypts the password before adding it to the server profile.

For the ODBC interface:

ENGINE SQLDBC SET CONNECTION_ATTRIBUTES CON1 SAMPLESERVER/MYUSER,PASS

For CLI interface:

ENGINE SQLDBC SET CONNECTION_ATTRIBUTES SAMPLESERVER/MYUSER,PASS

x

The syntax for the CONNECTION_ATTRIBUTES command for this adapter has been enhanced to include a logical connection name that is designed to support the porting of applications from development to production environments. This enhanced syntax may necessitate the migration of existing CONNECTION_ATTRIBUTES commands.

The Web Console Migrate option migrates your server settings to the newer release. To access this option, select Workspace, then Configuration/Monitor from the menu bar. Right-click Migrate from the Server folder in the navigation pane, and select Configure. On the Migrate pane, type the full path of the configuration instance directory (EDACONF) and click the Migrate button. This is the recommended approach.

If you choose not to use the Migrate option, please note the following information:

• Connection names declared prior to Version 7 Release 6.1 are supported.
• If you create a new connection for the purpose of creating new synonyms, your existing connections are re-saved in a new format, and the existing synonyms continue to work without any changes.
• If you add a new connection for the purpose of using an existing synonym, you must change the default logical connection name to match the value that is stored in the existing Access File attribute CONNECTION=value.

  For example, suppose that prior 7.6.1 the connection was defined as:

  ENGINE SQLDBC SET CONNECTION_ATTRIBUTES DSN_A/uid,pwd

  When synonyms based on objects stored in this DSN_A are created, the Access Files contains the following description:

  CONNECTION=DSN_A

  If you then add a new connection, you must change the connection name from the default CON01 to DSN_A and save it as DSN_A in order to reuse the existing synonym. The connection is stored in the profile as:

  ENGINE SQLDBC SET CONNECTION_ATTRIBUTES DSN_A DSN_A/uid,pwd

x

ENGINE SQLDBC SET DEFAULT_CONNECTION connection

where:

SQLDBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

connection

Is the connection defined in a previously issued SET CONNECTION_ATTRIBUTES command. If this name was not previously declared, the following message is issued:

FOC1671, Command out of sequence

Note:

• If you use the SET DEFAULT_CONNECTION command more than once, the connection name specified in the last command serves as the default connection.
• The SET DEFAULT_CONNECTION command cannot be issued while an uncommitted transaction (LUW) is pending. In that case, the following message is issued:

  FOC1671, Command out of sequence. 

Top of page

Example: Selecting the Default Connection

The following SET DEFAULT_CONNECTION command selects the database server named SAMPLENAME as the default database server:

ENGINE SQLDBC SET DEFAULT_CONNECTION SAMPLENAME

x

ENGINE SQLDBC SET AUTODISCONNECT ON {FIN|COMMAND|COMMIT}

where:

SQLDBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

FIN

Disconnects automatically only after the session has been terminated. FIN is the default value.

COMMAND

Disconnects automatically after each request. Depending on how often the event occurs, the SET AUTODISCONNECT command may result in considerable overhead. Almost all of this overhead is not related to the server. It is related to the operating system and the data source.

COMMIT

Disconnects automatically only after COMMIT or ROLLBACK is issued as a native SQL command.