Push Agent limits at Central Distributor

How many Distributor Agents (Distrib.exe files) SQL Server 2000 work better?
There is any limits?
Message posted via http://www.droptable.com
I'm not aware of any limits. For me, the issue is one of ordering of
transactions and isolation of publications. IE if you use a shared agent,
the transaction order is maintained which is not the case with independant
agents. The flipside is that an error which stops the shared agent will stop
it delivering transactions for all its publications until it is fixed.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||I've scaled it beyond 200, but that was with a pull, not a push. You get
better scalability with a pull. When you start approaching high numbers you
need to tweak this key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\SQL2000\SQLServerAgent\Subsystems\Distribut ion and set the value
C:\Program Files\Microsoft SQL
Server\MSSQL$SQL2000\BINN\SQLREPSS.DLL,C:\Program Files\Microsoft SQL
Server\80\COM\DISTRIB.EXE,ReplStart,ReplEvent,Repl Stop,100
where you Modify 100 to be the number of simultaneous distribution agents
you expect.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Krisnamourt via droptable.com" <u21487@.uwe> wrote in message
news:66e155dcf7428@.uwe...
> How many Distributor Agents (Distrib.exe files) SQL Server 2000 work
> better?
> There is any limits?
> --
> Message posted via http://www.droptable.com
>