Parallel DSI Threads for Microsoft SQL Server Replicate Database

In a heterogeneous replication environment, parallel DSI must ensure that the commit order in the replicate database is same as in the primary database.

DSI can then resolve deadlock conflict, when deadlock has occurred, and Replication Server can rollback transactions and execute again.

Replication Server can maintain the order in which transactions are committed and detect conflicting updates in transactions that are simultaneously executing in parallel either:
For external commit control, you must follow these rules:

Internal commit control method is better than external commit control because it depends on fewer conditions. If a deadlock occurs, the internal commit control allows Replication Server to roll back a single transaction, whereas external commit control rolls back all transactions.

Replication Server provides other options for maximizing parallelism and minimizing contention between transactions. For example, transaction serialization methods allow you to choose the degree of parallelism your system can handle without conflicts.

For detailed information on how to use parallel DSI threads, see Replication Server Administration Guide Volume 2 > Performance Tuning.