Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Why is SF_Replicate necessary after a database migration to a new server?

I had the database admin team copy my database hook line and sinker from an old to a new server. This means the DBAmp procedures, my local tables of SF objects, the last refresh times and all config was all faithfully copied over.

On the original server, I use the 'subset' option with SF_Refresh so it is not an issue that the local database table and the SF object definition have differing columns.

On the new server, these differences now cause an error even though I continue with my use of 'subset'. Why does DBAmp now have a problem? How did it get disrupted by a full database move - assume not all state it refers to is within that database?
1 person has
this question
+1
Reply