February 12, 2009 at 6:10 am
Hi guys,
I am in the process of changing our database to Unicode. I have all my scripts completed but I am unsure on which collation to use for Unicode. As well, once I do change it the collation on the database level, I have some collations on columns, how do I go about removing them?
Thanks,
D.
February 12, 2009 at 6:31 am
When you say changed ur scripts, what exactly was there on a script change, changed all data type to unicode 🙂
February 12, 2009 at 6:35 am
You should be able to change at the database level most langauges you want and you could do the same for the tables. It was not easy to change before 2008 but after I installed 2008 I could change both 2005 and 2008 collation at the database properties.
You should also change the .sql file save button in SMS click on the arrow and there you can also save all your scripts to most languages you want.
Kind regards,
Gift Peddie
February 12, 2009 at 8:01 am
We took our 2005 database and scripted it to create scripts to use Unicode, nvarchar, etc. So we have our unicode database created, just need to know the actual database collation to use?
February 12, 2009 at 8:20 am
Then I need countries and languages to give you collation because some langauges have more than one defined, like English.
Here are the two relevant links with definition and related langauge and country.
http://msdn.microsoft.com/en-us/library/ms144250.aspx
http://msdn.microsoft.com/en-us/library/ms143508.aspx
Kind regards,
Gift Peddie
February 12, 2009 at 8:39 am
Thanks for the links. Just one question, our database is currently in English. So the reason we switched to Unicode was to accept other languages. So is there one collation I can use to accept everything. Or say if the database needed to be in Chinese, I would have to choose the Chinese collation, is that how it works.
Sorry for the confusion.
Thanks,
D
February 12, 2009 at 8:56 am
No but in Europe minus Greek you can try this collation SQL_Latin1_General_Cp850_CI_AI_KI_WI and run some tests, And in Asia in China you need one for each version of Chinese and same with Japanese both langauges comes with more than 2500 characters alphabet. Then the right to left languages are different which includes Arabic and Thai.
SQL Server uses UCS-2 which is like UTF-16 but in 2008 the bytes of Nchar/Nvarchar is the same with the .NET Char. I can answer most relevant questions it is best to start with translated text and accept inserts for each langauge. One language per table is acceptable because you can use the collation in your DML(data manipulation langauge).
Post again if you still need help.
Kind regards,
Gift Peddie
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply