It is recommended for new Dynamics GP installs with SQL_Latin1_General_CI_AS.
If existing clients have different collations i.e. Latin1_General_CI_AS would it be necessary to change to the recommended collation using the BCP process, or is it better just to leave the collation as first installed.
The databases will be moved to a new Server, so there is an opportunity, but wondering if this is necessary to change, given the database is getting large.
Regards,
Mick
*This post is locked for comments
Richard,
This is where I suspect the collation issue arises with the long time customers.
The new collation should have displayed as : SQL_Latin1_General_CP1_CI_AS, typo in original post.
Mick
By the way, I often run into the wrong collation sequence with clients who had early versions of GP. Back when it was SQL 6.5 or 7.0 the other collation sequence was all GP supported.
Richard,
Thanks for the clarification.
Regards,
Mick
Over the years whenever I run into something other than the default collation sequence for SQL I have proposed switching it back for our clients. They often got tired of the case sensitivity or you switch resellers and the new reseller just assumes it is the default until somthing goes wriong and then they wind switching it anyway. The process is pretty straight forward so I would suggest doing it now before the database grows even larger.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156