The SQL collations are only there for backwards compatibility and should have stopped being the default many versions ago.
We always teach admins to use the Windows collations (ie: ones without a SQL prefix) rather than the SQL collations. Now that Latin1_General_CI_AS has become the default, I had used it for the new samples for 2016 (Wide World Importers). The product group got me to change it to Latin1_General_100_CI_AS as they said that’s the one they now prefer. (In which case, why isn’t it the default you ask…) Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/> From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Sunday, 12 June 2016 12:38 PM To: ozDotNet <ozdotnet@ozdotnet.com> Subject: SQL Server Collation I'm installing SQL Server 2016 Express for the first time to try it out. It's asking me for a default collation and its default is Latin1_General_Cl_AS. Is this a good default, or are there better choices? I know it might be a complicated argument. I thought I'd check first with the SQL boffins in here before I continue as I think the default get baked into the install forever (does it?) -- GK
