Page Comparison

In all replications, the source database must be an Oracle database. Therefore, two-way replication with MS SQL Server is not supported. ODBC connection is used to connect to MS SQL, thus two DSN (Data Source Name) with the same name must be set up setup by the system administrator on both source and target systems.

Using the correct Snapshot Isolation

Snapshot isolation must be enabled by setting the ALLOW_SNAPSHOT_ISOLATION ON database option before it is used in transactions. You must enable snapshot isolation in each database that uses it with the Transact-SQL ALTER DATABASE statement. In this respect, snapshot isolation differs from the traditional isolation levels of READ COMMITTED, REPEATABLE READ, SERIALIZABLE, and READ UNCOMMITTED, which require no configuration. The following statements activate snapshot isolation and replace the default READ COMMITTED behavior with SNAPSHOT:

ALTER DATABASE MyDatabase
SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE MyDatabase
SET READ_COMMITTED_SNAPSHOT ON

To check what the current snapshot isolation level, run the following SQL:

If the query returns 0 then it is turned off.

select name, snapshot_isolation_state_desc, is_read_committed_snapshot_on from sys.databases

See the child page Setup Wizard below for details of the configuration steps.If both source and target databases are running on Windows platform then DSN (Data Source Name) with the same name are required on source and target machine. But if source is Linux then DNS is only required on Windows target machine.