Good Day All
We have multiple publications on the same DB resulting in deadlock on the merge system tables due to the amount of subscriptions we have connecting to the server.
(not best practice/supported but nothing we can do about it)
We have been told to configure a max_concurrent_merge setting to limit the concurrent subscription connections.
When configured any connections over the max value get queued and then get processed as other subscriptions get processed.
My concern is that the polling interval is quite low for this publication and we might end up with the queue that is continuously growing if the subscriptions cannot be processed fast enough.
Is there a way to view the length of the queue if we do configure this for a publication?