Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The UTF-8 characters (nearly a million records) were imported into varchar(max) as western european. Is there any known method of fixing this in SQL? We have verified that the "garbage" characters that are showing up are, in fact, based on the incorrect characters in the Western European encoding representing the UTF-8 hexidecimal values. It would seem that the underlying hexidecimal in varchar field is correct. Ideally we would like to be able to fix this in SQL rather than re-importing the data.

share|improve this question

You'll need to re-import the data directly into an nvarchar column.

share|improve this answer

I've only seen application-side coding conversions used to fix the scenario you described (converting from UTF-8 to UTF16 or UCS2 format).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.