I have an issue make me sick with Encoding in SQL Server 2000.
1. I have a database (db1) with tables saved data with Windows-1252 Encoding
2. Now I want to migrate data from db1 to db2, but I want to store data in db2 is UTF-8. I try to search this similar expriences but found nothing, so, who have this expriences with that can share with me?
SQL Server does not support UTF8 character set.
The facade MS is holding is "if you have multi lingual requirements you should use double byte strings (as in NVARCHAR, NTEXT and NCHAR).
What can you do?
First you need to check if you need to support multi lingual data? I most cases there is no such requirement so all you have to do is to create an SQL Server database with a collation that will support the language you need it to store, then move the data trough DTS.
I hopes this helps,
In case post additional questions please send me an e-mail to email@example.com since I do not monitor this thread.
UTF-8 is not a data type, it is an encoding standard. UTF-8 can not be handled at the datatype level like INT, DATETIME, and FLOAT can. UTF-8 must be handled by the code that interprets the data.
Since DB2 is the name for a database engine, I'm going to use the word database for my question.
Is your problem that you have character data from the 1252 code page stored in Unicode columns in database 1, but you want to store the same data in non-Unicode columns encoded using UTF-8 in database 2?
I am moving data from snitz forum database to new database. My old snitz forum when saving data from website to database used windows-1252 codepage to store data (Of course save in nvarchar and ntext column). My new website save data with Unicode encoded. So, because it's just 140,000 records and I decice to write a very simple application to convert it.
Here are my sample application
1. I added more column in destination table: update_status (int), and update it to 0