January 6, 2004 at 1:57 pm
What is the largest number of replicated databases you’ve seen on a single server? Or, do you have an educated guess as to how many is too many?
We’d like to replicate several hundred from a single Publisher using a single remote Distributor.
Apparently a very large number of agents on a single server (Distributor) causes deadlocking in Tempdb (see KB link below). But it is not clear at what number of agents or volume of activity problems get bad.
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q246/3/30.asp&NoWebContent=1
Thanks! January 6, 2004 at 4:12 pm
I've had as many as 250 on one server. You do get contention, not to mention the resource use of 250 log readers running. I ended up writing some code that loops through each replicated db and runs the log reader. That way I have no contention, only one log reader. Greater latency of course.
January 9, 2004 at 8:22 am
How great was the latency in relation to overall transactions/sec?
I've fielded widely varying opinions about this. A MS consultant suggested no more than 10 agents (executables) per instance. That seems low to me, but perhaps that's wishful thinking.
I've put hundreds of databases on a single server, but the requirement I've been given to replicate so many at once (150+) is new to me.
Can anybody else weigh in on the number of replicated databases per server in your environment?
Eric
January 9, 2004 at 5:38 pm
Honestly never mentioned it. Our business process allowed for a fair amount of latency, so I loop through all db's once every 30 minutes. Job probably finishes in 5-6 minutes on average. You could easily cut that by a factor of 5-10 by running up to 10 logreaders at a time across all your db's - essentially each would do a chunk of the db's available.
Sometimes there is a real need for "immediate" replication, in practice a delay is seldom noticed by the users. Kind of like the stock market quotes being on 15 min delay.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply