Archives of the TeradataForum

Message Posted: Mon, 26 Sep 2005 @ 12:37:59 GMT

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

Setting the character set to Unicode should be enough to store 2-byte characters as data in the column. Characters which require more than 2 bytes could / should be converted.

I guess Unicode is the only option on the server side (binary data types aside)?

It is more difficult to use Chinese characters in table and column names, compression value lists etc.

They are. On the client side (where utility runs) there are more options to choose from. You can have Unicode in a few flavors or you can have simplified or traditional Chinese character sets. Which one to use depends on your platform (network or channel attached), release version of the database and utilities, and, of course, requirements other applications impose. The choice of the client character set can be important for the collation (set of rules defining character comparison and ordering) used.

Release specific details can be found in diverse utility manuals and the DDL SQL Reference for the server side settings.

Interesting topic to explore. Unlike Japanese, Chinese is "new" to Teradata.

Regards,

Victor

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