Re: MSmerge_history delivery_time seems wrong in 2000



The agent is running continuously and the history records are inserted
when the merge agent completes as expected. The duration of the agent
session should be between 10-20 seconds on my setup with the load that
is being generated.

In 2005 the values are correct, so this appears to be a 2000 problem.
Possibly in my environment only. (SQL Server 2000 SP4). Do the values
in your merge_history table on 2000 actually reflect the session
duration in seconds?

If so I might try testing on another server,

Thanks Jim Katsos.

.



Relevant Pages

  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... publisher/distributor running on the main office and a subscriber at the ... This is a new SQL Server 2005 behaviour, ... the agent should execute them (maybe the agent just ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: Network traffic with transactional replication with immediate updates (SQL 2005)
    ... publisher/distributor running on the main office and a subscriber at the ... the agent should execute them (maybe the agent just launches ... Looking for a SQL Server replication book? ... I cannot find a way to explain why Distributor Agents are to ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL Server 2005 replication monitor questions
    ... >> To get to the agents expand SQL Server Agent jobs, ... click on your publication in Enterprise ... >> bottom half you will see your snapshot and distribution agent. ... >> monitor it there (through replication monitor). ...
    (microsoft.public.sqlserver.replication)
  • Re: Server CE 2.0 Merge Replication
    ... This morning I am not able to access sscesa20.dll both from the emulator nor ... To change your connection settings, ... > your first goal should be to access the server agent from Pocket IE ... >> My SQL Server instance name be YYY ...
    (microsoft.public.sqlserver.ce)
  • Re: sp_replcmds
    ... It is possible that there is an open transaction ... Looking for a book on SQL Server replication? ... >> Stop SQL Server agent, restart it and see if this clears the error. ... Use Replication Monitor to view the details of> this ...
    (microsoft.public.sqlserver.replication)