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.
>
>

Large numbers of orphaned/expired requests

We are experiencing a situation where the SRS (2000 SP2) report server will no longer render reports. In the log file, there are many instances of

w3wp!runningjobs!434!3/23/2007-10:12:57:: i INFO: Adding: 8 running jobs to the database
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:13:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsExpired; found expired request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!434!3/23/2007-10:14:57:: i INFO: RunningJobContext.IsExpired; found expired request

What could be causing this? The reports are making queries through an OLE DB provider. There are no scheduled jobs, and the load doesn't seem that heavy.
Orphaned request indicates that the HTTP request has gone away before we finished processing the report. Generally this is because people request a report, and then close IE.