December 30, 2010 at 3:03 pm
I am upgrading a replicated database from SQL Server 2000 to SQL Server 2008, everything is transactional replication . Since I have the downtime I would like to rework how replication is setup on this server. Currently I have 4 different publications, 1 of which contains >80% of the tables that are replicated. I want to split that publication into 3 or 4 smaller publications to make maintenance easier going forward. Most of these publications have ~110 subscribers. With the default settings for SQL Server 2000 that instance has ~110 distribution agents running since there was only one distribution agent per subscriber. With SQL Server 2008 I believe it uses the independent agent setting by default which with my current setup could have me sitting at over 400 distribution agents, and if I split out the big publication like I want to I would be in the 600 - 700 distribution agent range, unless I am mistaken on how that setting works. Is that number of distribution agents going to be able to run, or will I need to force these use the shared agent setting? I have looked and I can't find anything relating to limits for this.
The system that I will be moving to is going to be running SQL Server 2003 x64, with dual 12 core proc's and 32GB ram.
December 31, 2010 at 9:39 am
So I think the number of concurrent jobs would be limited by the 'max worker thread' setting. And from what I can find with 24 cores that would be something like 832 threads. So I think I should be okay. I will definitely want to consolidate servers and try to reduce the amount of data that is replicated, but this should work.
Anyone have advice on how I could test this? I'm not sure how to create test jobs that just continuously runs.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply