Archives of the TeradataForum

Message Posted: Thu, 10 Nov 2005 @ 11:05:09 GMT

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

<-- Anonymously Posted: Wednesday, November 09, 2005 20:38 -->

The FORMAT reflects 10 CHARACTERS. The MaxLength reflects 20 BYTES to store those characters. Both are correct, since UNICODE (CharType 2 - see Data Dictionary manual) uses two bytes to store each character.

The ODBC API allows for the fact that display character length may not match internal byte (octet) length, and current versions of the driver should report this properly. I suppose you could trace at the ODBC side to see what is being returned to SQLDescribeColumn() or whatever ODBC call is being invoked directly or indirectly by MicroStrategy.

If the driver reports 20 characters, it's a Teradata client driver problem. If the returned data is correct but MicroStrategy is assuming that the byte/octet length is the number of display characters, it's a MicroStrategy problem.

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