Can compare be forced to use surrogate key defined in the config file (4299730)

Can compare be forced to use surrogate key defined in the config file.

General information.

Compare will only use the key that exists in the source and target databases. The surrogate key is only used by the Post process when posting to the respective target. Compare is not concerned with the surrogate key as it has to deal with both source and target table when comparing rows and in the process ends up using keys that are best suited for gathering and sorting rows to do that comparison. The actual keys existing for the tables on source/target are the best candidate and not surrogate keys which are only meant for posting and do not represent the keys for the source table. The “key” option of the Compare command only refers to the directive to compare source and target tables on the basis of key column and ignore the rest of the columns and has nothing to do with specifying one’s own key definition.