October 26th, 2004, 07:34 AM
|
|
Mad Rater
|
|
Join Date: Sep 2003
Posts: 126
Time spent in forums: 11 h 31 m 44 sec
Reputation Power: 7
|
|
Did you import the data using bcp? If so, note the following from the SQL server manual:
Quote:
Copying Data Between Different Collations
When bulk copying data using native or character format, bcp, by default, converts character data to:
* OEM code page characters when exporting data from an instance of Microsoft® SQL Server™.
* ANSI/Microsoft Windows® code page characters when importing data into an instance of SQL Server.
This can cause the loss of extended or DBCS characters during the conversion between OEM and ANSI code pages. To prevent the loss of extended or DBCS characters, bcp can create data files using:
* Unicode native data format (-N).
* Unicode character data format (-w).
* A specific code page (-C).
Unicode native format and Unicode character format convert character data to Unicode during the bulk copy, resulting in no loss of extended characters.
Using the -C (code page) switch, the bcp utility can create or read data files using the code page specified by the user. For example, to bulk copy the authors2 table in the pubs database to the Authors.txt data file using code page 850, execute from the command prompt:
bcp pubs..authors2 out authors.txt -c -C850 -Sservername -Usa -Ppassword
Alternatively, using the CODEPAGE clause, the BULK INSERT statement can read data files using the code page specified by the user. For example, to bulk copy the Authors.txt data file into the authors2 table in the pubs database using code page 850, execute from a query tool such as SQL Query Analyzer:
BULK INSERT pubs..authors2 FROM 'c:\authors.txt'
WITH (
CODEPAGE = 850
)
|
Hope this helps.
__________________
Up the Irons
What Would Jimi Do? Smash amps. Burn guitar. Take the groupies home.
|
ASP Free Forums Sponsor:
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
