Sometimes users may run two replication tools concurrently. This could be for a number of reasons such as testing, benchmarking, etc. This solution delves on the implications of doing this.
Need to consider resource contention when running two replication applications concurrently.
While Shareplex will be able to co-exist with other replication tools, the users may need to consider the impact of running two applications for performing similar tasks, namely replicating changes to the source databases. The most profound impact will be increased I/O since Shareplex's Capture process will have to contend with an equilvalent process from another application when gathering changes to the database. This is on the source. On target a similar situation will occur where Shareplex's Post process will be applying changes to the target database whereas a similar process from another application will be doing the same task. This may cause contention in the database. There may be resource issues such as memory and CPU when running two applications this way. So while running two different applications for replication will not interfere with each other the way some other applications (like virus protection) may, it can still be a resource drag because of duplication.
