SQL SERVER COLLATION TO SUPPORT CHINESE AND KOREAN LANGUAGE ALONG WITH ENGLISH

_{Monday, May 6, 2013 8:51 AM}

Hi,

I have my current location as SQL_Latin1_General_CP1_CI_AS, i have all columns in nvarchar.

Is there any collation which can support CHINESE AND KOREAN LANGUAGE ALONG WITH ENGLISH.

Thank you.

Thanks & Regards,
Manjunath C Bhat,
http://manjunathcbhat.blogspot.com
http://manjunathcbhat.wordpress.com

_{Monday, May 6, 2013 9:01 AM ✅Answered}

The collation settings regard only non-unicode data (char/varchar) and how they are handled (comparing, sorting, ...). For unicode data tpes (Nchar, Nvarchar) the collation doesn't matter and here you can always use multi-language/non-latin chars. In AdventureWorks database you can find some sample with multi-language support in the product description table.

Refer this useful link.

http://social.msdn.microsoft.com/Forums/en-US/sqldatabaseengine/thread/5fe66f7e-0676-403e-beda-5c01735afbfe/

Regards, RSingh

_{Monday, May 6, 2013 8:57 AM}

I think you can store CHINESE and KOREAN  charaters in nvarchar column.

It just that you can not create them with your english keyboard.

try copy pasting chinese characters from any site and again fetch them it will work

Thanks

Amey

_{Monday, May 6, 2013 9:03 AM}

Thank you all, it helped me a lot. thanks again.

Thanks & Regards,
Manjunath C Bhat,
http://manjunathcbhat.blogspot.com
http://manjunathcbhat.wordpress.com

_{Monday, May 6, 2013 10:31 AM}

As others have said, with nvarchar you can store data in Chinese, Korean, Quechua or whatever in nvarchar, no matter the collation. However, sorting and comparison rules may not be exactly correct.

When it comes to sorting, having multi-lingual data presents a problem, particularly for languages that use the same script. If they use different scripts like Chinese and Korean, there are better odds for co-existance.

There is one trap to watch out for: not all code points are defined, and in the 80 collations (those with no version number), there are fewer defined code points than in later code points. I know that this cause puzzling behaviour with Indian language, as these characters are not covered by the old collations like SQL_Latin1_General_CPI1_CI_AS.

I would recommend that you use any of the collations listed by this query:

select * from sys.fn_helpcollations() where name like 'Chinese%100%CI_AS'

As for which, I am not really qualified to tell. But Simplified is what they use in mainland China, whereas Traditional is in use in Taiwan.

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se