Yes, I would go with merge replication if I were you for such a topology.
"Lauren" <Lauren@discussions.microsoft.com> wrote in message
news:4DD2E911-6CA4-4DB4-B26C-97C581738708@microsoft.com...
> We are going to have 115 subscribers to 6 publishing servers so I would
> imagine that would cause problems if I went with updatable.
>
> Thankyou for you response,
> Lauren
>
> "Hilary Cotter" wrote:
>
>> Its a design limitation. The queue agent seems cause a lot of deadlocks
>> when
>> you start loading up the subscriber or if you have a large number of
>> subscribers. This is documented in Books on Line.
>>
>> --
>> 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 >>
>>
>>
>> "Lauren" <Lauren@discussions.microsoft.com> wrote in message
>> news:D9EFC511-A444-442B-B206-D0927E870012@microsoft.com...
>> > Hi Hilary,
>> >
>> > I noticed in a previous thread that you state that "Queued updating
>> > does not scale well when you have a significant portion of your DML
>> > occurring on the subscriber" - could you explain to me why that is?
>> >
>> > Regards,
>> > Lauren
>>
>>
>>