Store unicode characters in a Microsoft SQL database then display them on a web page

There are two ways that Unicode (specifically, Chinese) characters are getting entered into my Microsoft SQL database:

1. A user located in Taiwan is typing directly into a web form on a Windows computer that has Chinese as its default language, then my ASP script writes the result to the database.

2. A user located in the U.S. on a Macintosh has an Excel spreadsheet of language translations, which gets saved to a CSV file, uploaded to the server, then an ASP script processes that file and writes to the database. The actual characters in the Excel file come from a variety of sources: via e-mail from Taiwan, a Word or Excel file from Taiwan, or sometimes from Google Translate (via the web).

When I read from the database and display the text on a web page, here is what happens:

Using ASP, I insert this code at the top of my page: response.CharSet="UTF-8"
In the <head> area of the page, I also insert this: <meta charset="utf-8">

With only that, here is my test page:

The text from the U.S. computer is just question marks, the text from the Taiwan computer looks fine.

Next, I try adding another line of ASP code at the top of my page: response.CodePage=65001

Here is the result:

Now, the text from the U.S. computer looks fine, but the text from the the Taiwan computer is garbage.

From what I understand, response.CodePage=65001 is the same thing as UTF-8.

When I try selecting the text via a SQL Management Studio query window directly, I see the U.S. computer text looks fine, but the Taiwan computer text is garbage.

At this point, I am lost. I need to get a web page to display both of these types of text correctly, on the same page.

My assumption is that there is some difference between the character set on the U.S. computer vs. the Taiwan computer… that even though they are both Chinese, they are different versions of Chinese? If the data were exactly the same type, they should display the same on a web page.

Also, why adding response.CodePage=65001 flip-flops the success of those two types of text is a mystery to me.

Note that when the U.S. text goes bad, its all question marks. When the Taiwan text goes bad, its garbage characters.

This page shows eight different Chinese languages in the default SQL setup:
… I don't know if that is related to my problem or not.

Would really appreciate any insight to this. Thank you!
Brad BansnerWeb DeveloperAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Brad BansnerConnect With a Mentor Web DeveloperAuthor Commented:
I found the problem… it was unrelated to SQL. The Unicode was being garbled by a multi-part form using ASP Upload (Persits Software)… it was garbled before it even got to the SQL database. That software component has a fix, a line of code I needed to add to force it to accept Unicode. Problem solved!
try this place it before the doctype, first thing on the page

Response.CodePage = 65001
Response.CharSet = "UTF-8"

Open in new window

Brad BansnerWeb DeveloperAuthor Commented:
I don't think you could have possibly read my question.
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to and use offer code ‘EXPERTS’ to get 10% off your first purchase.

i take it from that it didnt work, but being rude to someone trying to help doesnt encourage them to put further effort in
Brad BansnerWeb DeveloperAuthor Commented:
Sorry. As I explained I already tried that and a variation of the same thing… its a little more complex of an issue than just adding a CodePage and CharSet, it has something to do with the data in SQL, I am pretty sure.
You could try specifying the language as Chinese with:

<META HTTP-EQUIV="Content-Language" content="ZH">

You might also be get the problem because of a non-strick XHTML doctype.  An html5 doctype might help.

Brad BansnerWeb DeveloperAuthor Commented:
I tried both of those, but no effect. I really believe SQL is storing two different types of data, I just don't know how to get a handle around what exactly I have.

Even if I have two different languages coming from two different SQL queries, a UTF-8 should be able to handle both of those on the same page, shouldn't it?
The only additional thing I can think of is that there is a problem with the collation sequence of the database.

This is a little old but it looks like a good place to start if collation is contributing to the problem:

Brad BansnerWeb DeveloperAuthor Commented:
Thanks for everyone's help, but I guess the right thing to do is select my own solution, since this particular problem was related to a Windows component, and not SQL or my page encodings.
Brad BansnerWeb DeveloperAuthor Commented:
Found solution on my own.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.