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

SF_Refresh ignoring Schemas and causing errant behavior.

SF_Refresh misbehaves if the database contains tables with the same name in a different security schema. In our environment, we have a second set of tables in a different schema. One of the tables is "Account", which seems to cause the SF_Refresh script to fail for the like named Salesforce table, reporting that the table has schema changes and requires replication. This is not the case, the script is simply looking at the wrong table for comparison.
1 person has
this problem