Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
awu25
Starting Member
1 Post |
Posted - 2004-08-02 : 05:23:47
|
| I have SQL Server installed on an English OS. I have a client with Chinese XP OS and Enterprise manager installed. I need to import a text file with Chinese text. When importing manually from Enterprise Manager on Chinese XP connecting to the Sql Server 2000 installed on the English 2000 OS everything imports fine. But if I simply create a DTS to do the import it imports garbarge. |
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2004-08-02 : 08:48:42
|
| Is it a Unicode text file?Mark |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-08-02 : 10:20:41
|
| It has to be a unicode text file imported into unicode fields. DTS will use the language of the OS, so to support Chinese characters using DTS, you must use Unicode.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2004-08-02 : 11:44:04
|
| Absolutely Derrick; Life would certainly be simpler if everybody used Unicode!However, quite often, the data files we receive from Asian clients have been encoded via other means. For example, GB2312-1980 (the National Standard of the People's Republic of China) or Big5 (used in Taiwan and Hong Kong) to name a couple.We generally import these via BCP/DTS Bulk insert task, specifying an appropriate codepage.Mark |
 |
|
|
|
|
|