Advanced Options | ODBC Driver for Teradata - Teradata ODBC Driver Advanced Options - ODBC Driver for Teradata

Enter the value used to try to limit the database response buffer size for SQL requests. This value can be adjusted dynamically if the database cannot send a result within the limited packet size defined.

See the “MaxRespSize=” option in Teradata DSN Options.

Lists the port number to use to access the database. Do not change this value unless instructed to do so by your DBA.

See the “TDMSTPortNumber=<integer>” option in Teradata DSN Options.

Lists the port number to use to access the database via TLS connection. Do not change this value unless instructed to do so by your DBA.

See the “HTTPS_PORT=<integer>” option in Teradata DSN Options.

Defines a value corresponding to the number of seconds to wait when establishing a virtual circuit with the database for login. Enter an integer value.

See Teradata DSN Options.

Activates the print option when creating stored procedures.

See the “PrintOption=[N | P]” option in Teradata DSN Options.

Specifies the SPL option when creating stored procedures.

See the “SplOption=[Y | N]” option in Teradata DSN Options.

Data Source DNS Entries=undefined (default setting) is recommended for best results. This setting enables ODBC Driver for Teradata to lookup DNS dynamically and find all available COPs for a given database name. Using this approach, ODBC Driver for Teradata will automatically detect new nodes added to the database (and DNS) in the future, without ODBC modification.

Data Source DNS Entries= 0 indicates that DNS does not contain cop entries for the database name. The database name will only be resolved by itself. No attempt will be made to resolve using a cop suffix. This behavior can be desirable in an environment utilizing DNS to load balance. When DNS is used for load balancing, administrators can configure DNS to provide a different IP address or multiple IP addresses in different order each time the database name is resolved using DNS.

Data Source DNS Entries= value. Entering a non-zero value indicates that DNS contains cop entries for the database name and the last cop entry is value. The first connection attempt will chose a random number between 1 and value. Each subsequent connection will then increment to the next number (round-robin). This approach will not encounter costly DNS resolution failures (how costly depends on how the DNS is configured). However, if additional entries are added to DNS at a later time, they will not be discovered by ODBC Driver for Teradata unless the supplied value is increased.

Enter the value used to set the maximum size of any one SLOB (CLOB, BLOB) item.

Valid for the database DSN in ODBC Driver for Teradata.

Transmission Control Protocol (TCP) provides an option called TCP_NODELAY to control the transmission of data.

See the “TCPNoDelay=[Yes | No]” option in Teradata DSN Options.

When this option is selected – NULL values are assumed for the Catalog Name parameters in any of the Catalog API functions, even if the application passes a value.

When this option is cleared and a value is passed for the Catalog Name parameter instead of NULL – ODBC Driver for Teradata returns an error because catalogs are not supported by the database.

When this option is selected, ODBC Driver for Teradata reads ahead by requesting the next response message from the database when the current response message being processed is not the last. The database can have one request active for each session at any point in time. An active request is either an SQL request which is executing or a request for the next part of the result from an earlier SQL request.

When this option is cleared, ODBC Driver for Teradata only requests the next response message from the database when the current response message has been processed by the driver.

When this option is selected, ODBC Driver for Teradata is responsible for retrying the socket system calls when they have been interrupted by some event such as a SIGALRM.

When this option is cleared, ODBC Driver for Teradata returns an SQL_ERROR to the ODBC Application. The ODBC Application is responsible for recovery from the interrupted socket system calls.

Enter the value used to set the maximum size of all LOB bytes per row.

When this option is selected– ODBC Driver for Teradata is directed to send DATE data for parameters bound as SQL_C_TIMESTAMP and SQL_TIMESTAMP.

This option should not be enabled for applications that are not using Microsoft Access Jet databases.

This option should only be selected for this circumstance, as this results in truncation of SQL_C_TIMESTAMP data to contain only the DATE portion.

Provides backwards compatibility for ODBC 2.x applications that have taken advantage of a defect in ODBC Driver for Teradata where the functionality of the Catalog APIs are non compliant with the ODBC Programmer's Reference specification.

The behavior when a NULL value is passed to the SQLTables API for the SchemaName argument results in a search for tables belonging to the userid, DBC, and default database schema names, rather than a % search pattern as noted in the ODBC Programmer's Reference specification.

Returns an empty string for the CREATE_PARAMS column of SQLGetTypeInfo for SQL_TIMESTAMP data type, and disallows MC-ACCESS from using any TIMESTAMP precision value in Create Table text.