Re: Push Agent limits at Central Distributor
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Tue, 26 Sep 2006 16:30:55 -0400
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\Distribution 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,ReplStop,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 SQLMonster.com" <u21487@uwe> wrote in message
news:66e155dcf7428@xxxxxx
How many Distributor Agents (Distrib.exe files) SQL Server 2000 work
better?
There is any limits?
--
Message posted via http://www.sqlmonster.com
.
- References:
- Push Agent limits at Central Distributor
- From: Krisnamourt via SQLMonster.com
- Push Agent limits at Central Distributor
- Prev by Date: Re: Push Agent limits at Central Distributor
- Next by Date: Re: how to restart replication after a key violation failure is fixed?
- Previous by thread: Re: Push Agent limits at Central Distributor
- Next by thread: Re: can sqlsvr2005 replicate tables to sqlsvr2000?
- Index(es):
Relevant Pages
|
