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 |
|
k_sekhar_rao
Starting Member
8 Posts |
 Posted - 2003-04-10 : 06:04:27
|
| Hi all,I am trying to upgrade my databases in sql server 6.5 to sql server 2000. I have no problems in data transfer. But the problem is with chinese characters. I have some tables with chinese characters in sql server 6.5. When i upgrade, chinese characters are replaced by some junk characters. i have defined the column of chinese characters as VARCHAR in sql server 6.5. Could any body suggest me in this regard.Thanks in advance,sekhar |
|
|
samsekar
Constraint Violating Yak Guru
437 Posts |
Posted - 2003-04-10 : 06:19:44
|
| BOL Says..The easiest way to manage character data in international databases is to always use the Unicode nchar, nvarchar, and ntext data types in place of their non-Unicode equivalents (char, varchar, and text). BTW.. What is the collation set on the database.SELECT DATABASEPROPERTYEX('dbname', 'Collation')select name,collation from syscolumns where id = object_id('tablename')Sekar~~~~Success is not a destination that you ever reach. Success is the quality of your journey. |
 |
|
|
k_sekhar_rao
Starting Member
8 Posts |
Posted - 2003-04-10 : 06:46:30
|
hi sekar,Thanks for the response. I have declared the datype as varchar in sqlserver 6.5. If i try to upgrade with giving the option nvarchar, i am getting the same junk values in the DB. Thanks,sekharquote:
BOL Says..The easiest way to manage character data in international databases is to always use the Unicode nchar, nvarchar, and ntext data types in place of their non-Unicode equivalents (char, varchar, and text). BTW.. What is the collation set on the database.SELECT DATABASEPROPERTYEX('dbname', 'Collation')select name,collation from syscolumns where id = object_id('tablename')Sekar~~~~Success is not a destination that you ever reach. Success is the quality of your journey.
|
|
|
|
samsekar
Constraint Violating Yak Guru
437 Posts |
Posted - 2003-04-10 : 07:55:56
|
| Having nvarchar is the good practice for international databases, that is what i exactly want to point out. for your problem you check the collation of the database. Try this:ALTER TABLE tablename ALTER columnname COLLATE Chinese_PRC_CI_ASSekar~~~~Success is not a destination that you ever reach. Success is the quality of your journey. |
|
|
|
|
|
|
|
|
data transfer from sql server 6.5 to sql server 20