17.20 - Version 16.20 - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2022-06-21
dita:mapPath
uqj1639470627591.ditamap
dita:ditavalPath
nkw1500504256726.ditaval

Key Features

  • JSON Web Token (JWT) authentication
  • UDF upload to Teradata Database
  • SET TRANSFORM GROUP FOR TYPE support for complex data types (CDT)

Key Changes in Product Behavior

Starting with version 16.20, ODBC Driver for Teradata 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 ODBC Driver for Teradata, and these features have been removed. For more information about the new driver and how its functionality compares to the previous versions of ODBC Driver for Teradata, see Deprecated Features for ODBC Driver for Teradata 16.20 and Later Versions.

This version of ODBC Driver for Teradata includes the following characteristics:

  • Deprecated features from the ODBC Driver for Teradata 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 ODBC Driver for Teradata 16.20 and Later Versions.
  • 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.
  • ODBC Driver for Teradata strictly adheres to ODBC specifications. Non-compliant ODBC functions found in old versions of ODBC Driver for Teradata 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 ODBC Driver for Teradata 16.20 Compatibility Reference.
  • ODBC Driver for Teradata conforms to standard ODBC 3.8 core level specifications.

Differences in Driver Implementation

There are differences between the old ODBC Driver for Teradata (16.10 and older) and the new driver's SLOB implementation. The new driver includes the following changes for SLOB 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 ODBC Driver for Teradata 16.20 Features.

Driver Migration

If you are migrating to the new driver from an old Teradata ODBC Driver (16.10 or older), update the Driver key to point to the newly installed driver.
If a user installs the same version of new and old drivers, the current ODBC Driver installation overwrites existing DSNs. Before a new ODBC Driver installation, make backup copies of DSNs first and then proceed with the installation. Once installation is complete, copy back the old DSNs.

On Windows, if the desired driver is Teradata ODBC DSN:

  1. 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:



  2. 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.

Key Changes in System Behavior

Key Change Description
16.20 Update 2 There are no key changes in system behavior for this release.
16.20 Update 1
ODBC-17927/TDS-99

Teradata Database version 16.20 Update 1 has native support for some of the ODBC Scalar functions. Thus, ODBC applications can use these scalar functions outside of the ODBC Escape Sequence syntax when the application is connected to the Teradata Database version 16.20 Feature Update 1 or higher.

For a complete list of functions, see "Scalar Functions" in ODBC Driver for Teradata® User Guide (B035-2526) version 16.20, April 2018.

16.20.00
N/A

The 16.20 version of ODBC Driver for Teradata 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 ODBC Driver for Teradata, see "New Teradata ODBC Driver Compatibility Reference" in ODBC Driver for Teradata® User Guide.

This version of ODBC Driver for Teradata includes the following characteristics:
  • Deprecated features from ODBC Driver for Teradata 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 "New Teradata ODBC Driver Compatibility Reference" in the ODBC Driver for Teradata® User Guide.
  • The ODBC Driver for Teradata installation is self-contained and the installation of other Teradata Tools and Utilities products such as Teradata ICU and Call-Level Interface (CLI) is not required.
  • Installing ODBC Driver for Teradata no longer automatically migrates DSNs. DSNs belonging to the older versions of the driver will not be converted to the newly installed version of ODBC Driver for Teradata. For more information, see "Driver Migration" in the ODBC Driver for Teradata® User Guide.
  • Supports the use of unixODBC and iODBC driver managers. This is in addition to existing support of Progress DataDirect Driver Manager.
  • ODBC Driver for Teradata strictly adheres to ODBC specifications. Non-compliant ODBC functions found in legacy versions of Teradata ODBC Driver are not supported by the new driver.
  • ODBC Driver for Teradata conforms to standard ODBC 3.8 core level specifications.

Deprecated/Removed Features

There are no deprecated or removed features for this release.