# DBAmp v2022 Collation issues **URL:** \ **Category:** CData DBAmp\ **Tags:** question\ **Created:** [July 11, 2023, 6:44am UTC](https://community.cdata.com/t/dbamp-v2022-collation-issues/241 "2023-07-11T06:44:40Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![andrew.wilson](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@andrew.wilson](https://community.cdata.com/u/andrew.wilson)\ **Post date:** [July 11, 2023, 6:44am UTC](https://community.cdata.com/t/dbamp-v2022-collation-issues/241/1 "2023-07-11T06:44:40Z")
Hi, We are migrating to new SQL 2022 servers.  I have installed v2022 of DBAmp on our new dev server, we use SF\_Replication/SF\_Refresh, changing to SF\_Mirror is not yet on the table.  My default server collation is Latin1\_General\_CI\_AS, and the DBAmp replicant also becomes this collation.  This is the exact same setup we run in production, with version 5.1.8.0 of dbamp.   Both environments, current prod and new dev have “Collation Compatible” and “Use Remote Collation” set to true. I have run a full SF\_Replicate, and when i start to run the daily SF\_Refresh i am getting the below error: --- Starting SF\_Refresh for Contact V8304 16:12:31: Using Schema Error Action of subsetdelete 16:12:37: Local table created at: 2023-05-17 16:29:00 16:12:37: Using last run time of 2023-05-17 16:29:00 Msg 468, Level 16, State 9, Line 1 Cannot resolve the collation conflict between “SQL\_Latin1\_General\_CP1\_CI\_AS” and “Latin1\_General\_CI\_AS” in the equal to operation. --- Ending SF\_Refresh. Operation FAILED. Msg 50000, Level 16, State 1, Procedure dbo.SF\_Refresh, Line 906 [Batch Start Line 0] --- Ending SF\_Refresh. Operation FAILED. Completion time: 2023-07-11T16:25:11.6757747+10:00 Any thoughts greatly appreciated?? ---
**Author:** ![Dani\_Moran](https://avatars.discourse-cdn.com/v4/letter/d/2acd7d/32.png) [@Dani\_Moran](https://community.cdata.com/u/Dani_Moran)\ **Post date:** [July 11, 2023, 9:34pm UTC](https://community.cdata.com/t/dbamp-v2022-collation-issues/241/2 "2023-07-11T21:34:46Z")
There has been an update to DBAmp that helps resolve that kind of collation issue. Please write in to [DBAmpSupport@CData.com](mailto:DBAmpSupport@CData.com) to get an up-to-date hotfix with the resolution included!