We currently have three main sql servers. Server sql4 (on prem) is our Publisher and Distributor and does push transactional replication to servers sql3 (on prem) and sql7 (ec2 instance AWS).
We have issues often with replication getting behind on the two subscribers. We are looking to see what our best options are for keeping current data on both sql3 and on sql7. We have other applications and databases on both sql3 and sql7, but are only replicating one database which is over one terabyte in size. We would like to know "in a perfect world" what the best way is to have current data on both the second on prem server and the server in AWS.
One option I know of is to set up a stand-alone distributor on prem, but I don't know how much of a difference that will make. I see deadlocks often between sql4 replication and other applications. If sql4 was NOT doing the distributing, would those deadlocks go away? If a stand-alone distributor did the distribution to the two subscribers, would that eliminate replication distribution deadlocks of the distributor did nothing else but distribute?
I'm open to any suggestions. I just want to eliminate the bottleneck and have the data be more consistently current on both the subscribers.
Thanks in advance for your suggestions.