The first thing to do would be to look for a line like:
“Starting SF_Mirror for Account V5.1.8“
The V5.1.8 indicates that the stored procedure being used here is still the v5.1.8 versions, which are incompatible with the newest version of DBAmp and its linked servers. Any vX.Y.Z version is going to be incompatible with v22 and onwards.
What you need to do to get around this is update the stored procedures. You can find the file “Create DBAmp SPROCS.sql” in the SQL folder of the CData DBAmp installation directory (make sure it’s the CData DBAmp/v22 installation directory, not your old version’s installation folder directory!). That script will create all the DBAmp stored procedures in whatever database you run it in, so be sure to run it in every database you would like to use with your upgraded version!
There is one extra step if you did not install DBAmp in the default installation directory. If that was the case, you will need to find all instances where @ProgDir is set in the Create DBAmp SPROCS.sql script and make sure it is set to the bin folder of your non-default installation directory. Once you make that edit, then you can go ahead and run it in all the databases you need them to be in.
