I'm testing merge replication between a SQL server 2000
publisher and multiple MSDE subscribers. The publication
consists of somewhere around 200 articles (tables, views,
store procs). All subscriptions are pull subscriptions.
My test environment has roughly 10 subscribers.
So far the solution seems to work nicely.
Does anyone know what kind of performance issues I may run
into if the number of subscribers increased to 50 or 100?
It there a theoretical limit or is it simply a question of
machine capability and band width?
Pat,
I haven't ever used more than a dozen simultaneous subscribers, but this
article details scaling up to 2000 subscribers and the correlation with
download speed, effect of RAM, processors etc:
http://www.microsoft.com/technet/pro...mergperf.mspx.
BTW, as far as I know there is no documented limit to the number of
subscribers.
HTH,
Paul Ibison
Monday, March 19, 2012
Limits on number of merge subscribers?
Labels:
2000publisher,
database,
limits,
merge,
microsoft,
msde,
multiple,
mysql,
number,
oracle,
publicationconsists,
replication,
server,
sql,
subscribers
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment