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 |
|
miranwar
Posting Yak Master
125 Posts |
Posted - 2003-10-16 : 12:47:38
|
| Hello,We are planning to upgrade our sale marketing system to support traditional chinese charaters Combined with english characters. Can anyone tell me what codepage should be selected during the Installation process for SQL 2000 ? Thanks for your help in AdvanceRegards, |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-16 : 12:52:15
|
| You could select the default collation. Then you could have you database design such that it supports both. You would want to use Chinese and Latin1 collations in your database design. From SQL Server Books Online:SQL Server 2000 supports objects that have different collations being stored in a single database. Separate SQL Server 2000 collations can be specified down to the level of columns. Each column in a table can be assigned different collations. Tara |
 |
|
|
miranwar
Posting Yak Master
125 Posts |
Posted - 2003-10-16 : 13:05:12
|
| Thanks for the quick reply really appreciate it I presume when you talk about the default collation it's the code page you are referring to. On the basis you use the default collation how can u manipulate the database design would you just have to declare all the schema to use Unicode ?If not using the default collationHow would you combine Chinese and Latin1 collations on one table wich would need to store chinese and english characters ?Thanks |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-10-16 : 14:07:35
|
| Have a look at code page described in SQL Server Books Online so that you can see what collations are. You would define the collation on each column. So you could have an English column for description and a Chinese column for description.Tara |
 |
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2003-10-17 : 07:48:48
|
With SQL 2000, you really shouldn't bother changing the collation at the server or the database level. Use column level collations only, it's more convenient this way.I suggest you leave even the column collation at the default, and use Unicode datatypes (nchar/nvarchar) for the Chinese columns. Its a *lot* less trouble! Owais Make it idiot proof and someone will make a better idiot |
 |
|
|
|
|
|