DBAmp v2022 Collation issues

  • 11 July 2023
  • 1 reply



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 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??


Best answer by Dani Moran 11 July 2023, 23:34

View original

1 reply

Userlevel 4

There has been an update to DBAmp that helps resolve that kind of collation issue. Please write in to to get an up-to-date hotfix with the resolution included!