Hello!
We are upgrading from Dynamics SL 2011 to SL 2015 and at the same time upgrading SQL server to v 2014, as the new version of Dynamics SL will not work on SQL 2008.
SQL 2008 has a collation set to Latin1_General_CI_AS whilst the SQL 2014 has the collation set to SQL_Latin1_CP1_CI_AS.
Our integrator is flagging this as an issue, seems they have to be the same.
Question then is will this collation difference be an issue or not?
TIA
Peter
*This post is locked for comments
Erich,
Thanks for your reply. Appreciate the insight.
If you don't have any international/foreign language data, it doesn't matter really. The above web site will explain what can happen if you do have foreign language data.
The code page, language code identifier and comparison style are all identical on these 2 collations.
We are using SL 2015 with SQL 2012 with collation SQL_Latin1_General_CP1_CI_AS without any issues for 4 months now.
As far as I know, the collation is a database level setting. This means that each database within a server has its own collation setting. There shouldn't be a problem to migrate the SL databases to the new server and re-create them with a Latin1_General_CI_AS collation.
There is indeed a server-level collation definition, but it reaches only the following:
This is the kind of things that appears in the "Before you begin..." section. This is so beause setting collates is as easy as I said in the moment the database gets created. If you try to correct it later you are in trouble. So, you should have a clear data migration procedure to sort this out.
Having said that, the problems that might arise are:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (