Latency in merge replication

Hi,
I have a merge replication (one publisher/distributor and one subscriber) and I am experiencing latency problems. When I modify some data in one of this servers, it takes about 40 secs to replicate this data. Is it possible decrease this time? I mean, 2 o
r 3 secs would be good.
Thank you
Marcos,
you can decrease the -PollingInterval if you are running continuously, which
makes a big difference. Other ways to optimise are listed in these articles:
http://www.microsoft.com/technet/pro.../mergperf.mspx
http://www.sql-server-performance.co...ion_tuning.asp
HTH,
Paul Ibison
"Marcos Federicce" <Marcos Federicce@.discussions.microsoft.com> wrote in
message news:AAFE1AE8-732F-4E5C-8EA6-24E1AB33BB18@.microsoft.com...
> Hi,
> I have a merge replication (one publisher/distributor and one subscriber)
and I am experiencing latency problems. When I modify some data in one of
this servers, it takes about 40 secs to replicate this data. Is it possible
decrease this time? I mean, 2 or 3 secs would be good.
> Thank you
|||right click on your merge agent, select properties, go to steps, click run
step and a the end of the string type
-PollingInterval 1
This should bring it down considerably, probably within 4s. YMMV
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Marcos Federicce" <Marcos Federicce@.discussions.microsoft.com> wrote in
message news:AAFE1AE8-732F-4E5C-8EA6-24E1AB33BB18@.microsoft.com...
> Hi,
> I have a merge replication (one publisher/distributor and one subscriber)
and I am experiencing latency problems. When I modify some data in one of
this servers, it takes about 40 secs to replicate this data. Is it possible
decrease this time? I mean, 2 or 3 secs would be good.
> Thank you
|||Paul,
The PollingInterval solved my problem. Thank you.
Marcos
"Paul Ibison" wrote:

> Marcos,
> you can decrease the -PollingInterval if you are running continuously, which
> makes a big difference. Other ways to optimise are listed in these articles:
> http://www.microsoft.com/technet/pro.../mergperf.mspx
> http://www.sql-server-performance.co...ion_tuning.asp
> HTH,
> Paul Ibison
>
> "Marcos Federicce" <Marcos Federicce@.discussions.microsoft.com> wrote in
> message news:AAFE1AE8-732F-4E5C-8EA6-24E1AB33BB18@.microsoft.com...
> and I am experiencing latency problems. When I modify some data in one of
> this servers, it takes about 40 secs to replicate this data. Is it possible
> decrease this time? I mean, 2 or 3 secs would be good.
>
>
|||Hilary,
It was better than I expected. Data is now merged no more than 2s.
Thank you
Marcos
"Hilary Cotter" wrote:

> right click on your merge agent, select properties, go to steps, click run
> step and a the end of the string type
> -PollingInterval 1
> This should bring it down considerably, probably within 4s. YMMV
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Marcos Federicce" <Marcos Federicce@.discussions.microsoft.com> wrote in
> message news:AAFE1AE8-732F-4E5C-8EA6-24E1AB33BB18@.microsoft.com...
> and I am experiencing latency problems. When I modify some data in one of
> this servers, it takes about 40 secs to replicate this data. Is it possible
> decrease this time? I mean, 2 or 3 secs would be good.
>
>

Last Queued Updating question....I think

When I setup my publication, I selected Queued updating. When I setup my Push, do I also need to select queued updating for the Subscriber as well?
Even though I have no intention of doing any updates on the Subscriber, I am only doing this because it was suggested as being the best option.
Please advise. I think this should be it for questions on this topic then....I hope.
JLS,
yes - this needs to be selected if your aim is a simple failover methodology and it'll only be available if you select the advanced options. If you don't select it then you end up with a non-updatable subscriber, which maybe isn't your main interest, but the implication of this is that you won't have automatic range management of identities on the subscriber and also no simple method of failing back to the publisher if necessary.
HTH,
Paul Ibison

Large delete stmt - 2nd question

Publisher has delete stmt executed against transactionally replicated table.
270K rows deleted in 1 stmt.
1 Subscriber connected with T1
How best to replicate all the 270K simpleton delete calls to
sp_MSdel_tablename at subscriber through distr agent? What parameter
adjustments to make?
Changed -CommitBatchSize to 1000, doesn't seem to increase speed much...
Thanks,
Chris
Set HistoryVerboseLevel to 0, CommitBatchSize to 1000 and
CommitBatchThreshold 10000
Hilary Cotter
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
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:DED73E09-DA75-444C-8976-96FF475B9567@.microsoft.com...
> Publisher has delete stmt executed against transactionally replicated
table.
> 270K rows deleted in 1 stmt.
> 1 Subscriber connected with T1
> How best to replicate all the 270K simpleton delete calls to
> sp_MSdel_tablename at subscriber through distr agent? What parameter
> adjustments to make?
> Changed -CommitBatchSize to 1000, doesn't seem to increase speed much...
> Thanks,
> Chris