Prior to registering a Compare Source environment, the following database relationships must be configured by your implementation's database administrator to match the diagram below:
Notice that there is no database relationship originating from the Compare Source schema back to the target environment's schema. This is because random keys added in a Compare Source are not kept in the target environment's key table (because the system does not guarantee unique keys between a Compare Source and a target environment).
Note: In Oracle, the database link defines privileges to the
remote database objects. The database link accesses the Compare Source database as CISREAD.
In DB2, the registration utility grants the target environment's
CISUSER database user read-only access
to a Compare Source environment's
database (a separate CISREAD database
user defined in the Compare Source
environment is unnecessary). In MS SQL Server, registration utility
uses fully qualified object name to the remote database objects.
The diagram below shows how the script table in a Compare Source environment's database is accessed by the target environment using a remote table synonym, prefixed with "R" in this case:
Figure 1. Compare Source Environment Tables Accessed Via Remote Table
Synonyms
