Migration Issues - ODBC Driver for Teradata

ODBC Driver for Teradata User Guide

Product
ODBC Driver for Teradata
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-07-11
dita:mapPath
smj1488824663219.ditamap
dita:ditavalPath
Audience_PDF_product_legacy_odbc_include.ditaval
dita:id
B035-2526
lifecycle
previous
Product Category
Teradata Tools and Utilities

Applications that migrate to an ODBC driver with Native LOB Support may now behave differently than before the migration. This might be related to the use of LOBs.

There could be two reasons for the difference in behavior:
  • The application relies on the ODBC feature that allows an application to query for all available types and uses that information to generate SQL
  • The application uses the ODBC types SQL_LONGVARBINARY and SQL_LONGVARCHAR

Applications that query for all types will now receive information about two data types (BLOB and CLOB). This may in some cases cause problems. See SQLGetTypeInfo.

Applications that are using SQL_LONGVARBINARY and SQL_LONGVARCHAR may behave differently since these types are now mapped differently.

If an application falls into one of the mentioned categories it may be appropriate to consider disabling the Native LOB functionality by setting UseNativeLOBSupport=No.

The option to set Native LOB Support is deprecated. For details, see Deprecated SQL Transformations