You’re offline. This is a read only version of the page.
30
I'm running a test upgrade from Dynamics GP 2010 to GP 2013
I've moved the Dynamics Database and one of our company databases to the new server but the upgrade fails. Looking online I think it's because the "production" machine has 3-4 companies on it, where I've only restored the Dynamics and one company (the smallest sized). So I found a script from the MDSN blog site on upgrading to remove databases not restored. But i'm getting the following error:-
Msg 468, Level 16, State 9, Line 3
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
I've found a few solutions but no idea where to add the COLLATE DATABASE_DEFAULT to the SQL script.
*This post is locked for comments
I have the same question (0)
This article will give you some background information on what is going on.
social.msdn.microsoft.com/.../server-collation-sqllatin1generalcp1cias-versus-latin1generalcias
You have a bigger problem because you have at least one database that is using a different collation sequence than the others. Looks like one server uses the older case sensitive collation sequence and the other used the case insensitive collation sequence. They need to use the same collation sequence,
I have always used the bulk-copy method to correct this but there are other methods. What this does is export the data out to ascii text files and then you import into a database with the correct collation sequence.
Here is an article that outlines the steps:
Share
Report
All responses (
Answers (
