You can configure Replication Server to apply transactions to the replicate data server in a heterogeneous environment using parallel Data Server Interface (DSI) threads. Applying transactions in parallel increases the speed of replication, yet maintains the serial order of the transactions as they are applied at the primary site.
Replication Server 15.5 introduces a transaction serialization method to improve performance and data integrity with parallel DSI for heterogeneous replication. In the new method, wait_after_commit, each thread waits to begin its first batch until the previous thread has completely committed. Sybase recommends that you use wait_after_commit serialization method for databases that use multiversion concurrency control (MVCC) or optimistic concurrency control (OCC), such as an Oracle database. Otherwise, you can use wait_for_commit as the default method.
Database |
Internal commit control method |
External commit control method |
|---|---|---|
Oracle |
Yes |
No |
Microsoft SQL Server |
Yes |
Yes |
IBM DB2 UDB |
Yes |
Yes |
See the Replication Server Heterogeneous Guide for detailed information about using parallel DSI for non-ASE databases.
