There is a performance cost associated with character set translation.
If you can set up an environment such that no character set translation is required, then you do not have to pay this cost, and your setup is simpler to maintain.
If you work with a single-byte character set and are concerned only with seven-bit ASCII characters (values 1 through 127), then you do not need character set translation. Even if the code pages are different in the database and on the client operating system, they are compatible over this range of characters. Many English-language installations will meet these requirements. In this version character set translation is turned on by default.
If you do require use of extended characters, there are other steps you may be able to take:
If the code page on your client machine operating system matches that used in the database, no character set translation is needed for data in the database.
If you can use a version of Sybase IQ built for your language, and if you use the code page on your operating system, no character set translation is needed for database messages. The character set used in the Sybase IQ message strings is as follows:
Language |
Character set |
|---|---|
English |
cp1252 |
French |
cp1252 |
German |
cp1252 |
Japanese |
cp932 (Shift-JIS) |
Also, recall that client/server character set translation takes place by default. Character set translation is disabled if you specify CharSet=none in the connection string.