Archives of the TeradataForum

Message Posted: Thu, 28 Jul 2005 @ 13:53:30 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

As far as I am aware 'UNICODE' is not a valid character set name for the ODBC driver.

Prior to ODBC 3.4 (TTU 8.0) and Teradata V2R6 the only Unicode session character set available in ODBC was 'UTF8'.

In 3.4 they added 'UTF16'.

You may also run into problems if you mix a version of ODBC that came from a different TTU than the version of SQL Assistant.

SQL Assistant 7.0 should use ODBC 3.4.0.x

SQL Assistant 6.x should use ODBC 3.3.0.x (or prior)

Normally this does not matter too much - but in TTU 8.0 SQL Assistant was changed to use the Unicode version of our ODBC driver... and only version 3.4 supports this Unicode interface.

(The Microsoft driver manager will take care of most conversions if you do use an older driver - but you will not be able to use unicode data since SQLA now expects ODBC to take care of that. [Previous versions of SQLA used to perform the required character set conversions.])

Mike Dempsey
Teradata Client Tools

	<Prev	Next>		<<First	<Prev	Next>	Last>>