MAXIMUM PUBLICATION LIMITATION IN SUBSCRIPTION

(1) do you mean the no of subscribers in a publication?
In that case the answer is no designed limit, and hte
merge optimization paper talks about scaling out to 1000s
of subscribers.
(2) have a look at the merge agent's profile for upload
and download changes per batch.
(3) this message doesn't look like an error, just a
warning based on the inactivity threshold of replication
monitor. My guess is blocking was the cause if it
completed after the others had synchronized. You can
verify this next time by running sp_who2 and looking at
the blocking column (or better still, sp_who3 if you have
it).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

>--Original Message--
>Hi,
>I am dealing with merge replication for 20 databases
(each of size 2 GB).
>Average transactions per day is 3000.
>1. I want to know, is there any limitations in the
number of publication
>that can be
> set in a subscription(now we have 20 DBs).
>2. The updates are merging in batches of 100 updates. Is
there any way to
>increase the batch size.
>3. There is a delay in merging of data in a particular
database(DB1), on
>that day
> totally more than 4,00,000 updates were done. Two
times the error
> message 'There is no response since last 30
minutes'. After completion
>of replication in other databases, DB1 starts
synchronizing. What is the
>reason for those errors.
>
>Thanks,
>Soura
>
>.
>
Hi,
Thanks for ur reply.
(1) I am replicating 2 servers(local & remote. Remote sr. is publisher &
local sr. is Subscriber). In that, currently 20 databases are replicated. I
am in need to replicate some more databases. Is there any limitation in the
numbere of databases to be replicated & is there any implications?
(2) Now the batch size is 100. I want to change this into some huge value.
Is there any implications due to this?
Thanks,
Soura
"Paul Ibison" wrote:

> (1) do you mean the no of subscribers in a publication?
> In that case the answer is no designed limit, and hte
> merge optimization paper talks about scaling out to 1000s
> of subscribers.
> (2) have a look at the merge agent's profile for upload
> and download changes per batch.
> (3) this message doesn't look like an error, just a
> warning based on the inactivity threshold of replication
> monitor. My guess is blocking was the cause if it
> completed after the others had synchronized. You can
> verify this next time by running sp_who2 and looking at
> the blocking column (or better still, sp_who3 if you have
> it).
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
> (each of size 2 GB).
> number of publication
> there any way to
> database(DB1), on
> times the error
> minutes'. After completion
> synchronizing. What is the
>
|||(1) no limit on the number of databases. The only
iomplication I would consider is the hit on the server
when all these merge agents are running, and I'd try to
ensure the schedules don't overlap as much as possible.
(2) setting the batch size it to a large value - each
batch is a transaction, so an error in one insert eg due
to connection failure - will cause the entire batch to
fail. For a large batch this could be an issue on some
networks.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thank u for ur reply.
"Paul Ibison" wrote:

> (1) no limit on the number of databases. The only
> iomplication I would consider is the hit on the server
> when all these merge agents are running, and I'd try to
> ensure the schedules don't overlap as much as possible.
> (2) setting the batch size it to a large value - each
> batch is a transaction, so an error in one insert eg due
> to connection failure - will cause the entire batch to
> fail. For a large batch this could be an issue on some
> networks.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>