You can also go with Latin1_General_CI_AI
The reason is that Unicode data is stored using NVarchar fields, SQL Server is more flexible because it can mix Varchar (1-byte) and NVarchar (2 bytes) data. Thus, to match UTF8, any mapping. As for CI - each individual sorting in 2008 allows you to add a CI specification (this is a checkbox in the "case sensitive" user interface - unchecked for insensitivity).
The last bit, and some others, such as width, are an additional setup on SQL Server.
Point number 2 from http://forums.mysql.com/read.php?103,187048,188748
utf8_unicode_ci is great for all of these languages: Russian, Bulgarian, Belarusian, Macedonian, Serbian and Ukrainian.
If you need sorting for a specific language, where languages ββhandle accents differently, you need a specific dictionary order - see here http://msdn.microsoft.com/en-us/library/ms144250.aspx . Otherwise, Latin1_General is based on Latin-American
RichardTheKiwi
source share