Good morning,
We are seeing some sporatic replication issues in a couple of our environments, This causes us to have to wait to it to either time out or a replication complete to run on the weekend.I know there are methods to stop these via running direct Queries into the DB with an accoujnt that has modify rights. Unfortunatley we don;t have a a quick and efficient way to do this as it involves engaging other teams and can take alot of time to accomplish.
What I am wondering is whether or not anyone has come up with a way via a report to stop these stuck replication runs so that we can clear things out and either wait for the next run to happen or kick it ourselfs on the server. I get the impression that when objects are in a stuck replication run they might not be able to be pushed by subsequent runs.
Anyone have any thoughts on this?
Thanks
DCHAD