April 7, 2015 at 3:51 pm
Hello
I have a problem with creating a new subscription.We have replication jobs for many database running from a distributor. When I added a new subscription, the snapshot job failed. Further troubleshooting we found that if we stop a different replication job, the snapshot runs fine. We have about 180 jobs running concurrently. Is there a limit we hit on replication jobs? can we change some setting to increase this limit?
we checked msdb..sysubsystems and the max_worker_threads is 1200 for replication jobs and almost all subsystems other than powershell its more than 1000.
please advise.
Thanks
April 7, 2015 at 8:42 pm
I'm not entirely sure this will help but found this article [https://ask.sqlservercentral.com/questions/24486/replication-limit-on-number-of-push-subsciptions.html] - I don't think there's an exact limit as much as there's a threshold with "load"
-Hope it helps!
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
April 8, 2015 at 7:46 am
Thanks for the reply.
We already have the work around set up and its running fine. I wanted to see if there were any fixes that I might be unaware of.
I am going to reach out to MS to see if they have any solution for this.
Thanks again
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply