August 6, 2021 at 11:41 pm
I have 500 databases on one SQL 2019 Enterprise Edition server. I want an AlwaysOn AG for HA with 1 replica.
Am I safe in calculating that SQL consumes 2 cpu threads for each database, therefore 1000 threads consumed just to manage 1 Always On replica?
Thank you in advance!
Chris Becker bcsdata.net
August 8, 2021 at 12:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 11, 2021 at 6:18 am
This was removed by the editor as SPAM
August 11, 2021 at 7:19 pm
I think that this page will help:
https://www.sqlshack.com/max-worker-threads-for-sql-server-always-on-availability-group-databases/
The link above says that for 500 databases with 1 primary, 2 secondaries, and 1 availability group your MINIMUM threads should be 1501. The maximum number of worker threads depends on the number of logical CPU's you have. By having only 1 secondary, you drop that down to a minimum number of worker threads of 1001 based on the calculations in that link.
That link has a really nice write up (not done by me) of worker threads and AG's. It is worth a read if you are looking to set up an AO-AG.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply