Multiple Primary Replication Paths

Create multiple primary replication paths from the primary database to one or more Replication Servers to increase replication throughput and avoid contention, or to route data to different Replication Servers.

Each primary replication path consists of a RepAgent path from the primary database to a Replication Server and an associated primary connection from the Replication Server to the primary database. You can bind objects, such as tables or stored procedures, to one or more of these paths.

A physical path defines the Replication Server that is going to receive data that you bind to the path, and the RepAgent sender thread that connects to the same Replication Server. Use the same connection name to associate the RepAgent physical path from the primary database to the Replication Server with the corresponding connection from the Replication Server to the primary database.

A logical path groups one or more physical paths under a single name to distribute data to multiple Replication Servers. If you need to replicate a table to multiple destinations, you can bind the table to a logical path that groups the relevant physical paths, instead of binding the table to the physical path for each destination

• Multiple Scanners
  Enable multiple scanner threads for RepAgent to take advantage of available replication paths and improve replication performance.
• Secondary Truncation Point Management
  To improve secondary truncation point management in a multipath replication environment, set the frequency of truncation point request intervals for Adaptive Server RepAgent.
• Creating Multiple Primary Replication Paths
  You can create multiple primary replication paths from the primary database to one or more Replication Servers. Each primary path consists of a RepAgent path and an associated primary connection.
• Enabling Multithreaded RepAgent and Multiple Paths for RepAgent
  Enable multithreaded RepAgent and configure it to use additional paths from the primary database.
• Creating Alternate Replication Paths for the Primary Database
  Use the add parameter with sp_replication_path to create alternate physical paths between the primary database and a Replication Server by associating a RepAgent replication path with a primary connection from the Replication Server.
• Creating Logical Primary Replication Paths
  Use the add and logical parameters with sp_replication_path to create logical primary replication paths that you can use to distribute data and objects bound to a physical path to multiple Replication Servers.
• Changing Configuration Values in a Replication Path
  Use the config parameter with sp_replication_path to set parameter values in alternate replication paths.
• Display Replication Path Information
  Use the list parameter with sp_replication_path at the primary database to display information on bindings and replication objects.
• Verifying Replication Path Usage
  Check the status of the DSI threads in the replication paths to ensure that the multipath replication system can use the replication paths.