I thought Dieter might be able to jump in on this one since his last name is really Doter with an umlaut over the o.
We are in the process of pulling data out of SAP ECC into a Teradata 13.10 database. I have defined one of the tables as follows:
CREATE SET TABLE DEV_SAP_POC.COUNTRY_TEXT ,NO FALLBACK ,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT
SPRAS VARCHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC,
LAND1 VARCHAR(3) CHARACTER SET LATIN NOT CASESPECIFIC,
TXTSH VARCHAR(20) CHARACTER SET UNICODE NOT CASESPECIFIC,
ODQ_CHANGEMODE VARCHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC,
PRIMARY INDEX ( SPRAS );
Note the third field is defined as UNICODE. I have also updated my ODBC driver to UTF16. When selecting from the table I am unable to display the umlaut over the A:
D ZA SÃ¼dafrika N 0
Generically speaking, what is the best way to store and access a special character umlaut?
Thanks in advance,
UNICODE should fix the issue. I am using following and i can see it properly when selecting:
My session character set is ASCII.
you probably just have a display problem, what tool are you using?
In SQL Assistant you need to set a font which actually includes Unicode characters, e.g. "Lucida Sans Unicode".
Btw, to store german Umlauts you don't need Unicode, they're also in the Latin charset.
The problem was actually a setting within Data Services. Once the setting was changed to utf16, I believe it fixed the problem. Thank you all very much for your responses!
btw... I was using SQL Assistant so it is good to know about the new font setting.