Starting with version 16.20, Teradata ODBC Driver has a new code base, and many of the features found in previous versions have been completely redesigned. The new driver does not include all of the deprecated features found in previous versions of the Teradata ODBC Driver, and these features have been removed. For more information about the new driver and how its functionality compares to the previous versions of the Teradata ODBC Driver, see Deprecated Features for New Teradata ODBC Driver.
This version of ODBC Driver for Teradata includes the following characteristics:
- Deprecated features from the Teradata ODBC Driver are no longer functional and are not supported in the new driver. There are no workarounds for these procedures, as they are obsolete. For a complete list of obsoleted features which do not work in the new driver, see Deprecated Features for New Teradata ODBC Driver.
- Starting with version 15.10.01.x, the Side-by-Side feature requires unique driver names for DSN-less connecting Applications in order to reference the different versions of drivers that may be installed. For more information, see MultiVersion Support.
- ODBC install is self-contained and the installation of other Teradata Tools and Utilities products such as Teradata ICU, Call-Level Interface (CLI), and TeraGSS is not required.
- Installing the ODBC Driver no longer automatically migrates DSNs.
DSNs belonging to the older versions of the driver will not be converted to the newly installed version of the ODBC Driver. See "Driver Migration" below for more information.
- Supports the use of unixODBC and iODBC driver managers. This is in addition to existing support of Progress DataDirect Driver Manager.
- Teradata ODBC Driver strictly adheres to ODBC specifications. Non-compliant ODBC functions found in old versions of TD ODBC driver are not supported by the new driver.
- As an important example of adherence to the ODBC specification, you must close the cursor before executing another query or else a cursor error is returned. Previously, you were able to bypass closing the cursor but this is not the correct behavior. This and other differences can be found in New Teradata ODBC Driver Compatibility Reference.
- Teradata ODBC driver conforms to standard ODBC 3.8 core level specifications.
Differences in Driver Implementation
- Caches, or attempts to cache, up to 2GB of all SLOBs in a row.
- Three configuration parameters:
- 1-Enable SLOB Random Access
- 2-Max size of one SLOB
- 3-Max size of all SLOBs in a row
For more information, and a detailed list of features in the new driver, see New Teradata ODBC Features.
Driver Migration
On Windows, if the desired driver is Teradata ODBC DSN:
- Change the key value under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\ODBC Data Sources from Teradata to Teradata ODBC Driver 16.xx as shown in the figures below.
From
To:
- Also change the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\Teradata ODBC DSN\Driver from C:\Program Files (x86)\Teradata\Client\15.10\bin\tdata32.dll to Teradata ODBC Driver 16.xx as shown in the figures below.
From:
To:
The DSN now points to the new driver.