Re: MSmerge_history delivery_time seems wrong in 2000
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Mon, 12 Jun 2006 22:04:48 -0400
Is your agent running continuously or scheduled. It could represent the time
the DML occurred as opposed to when it was merged.
--
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
"JIM" <jkatsos@xxxxxxxxxxxx> wrote in message
news:1150157954.170535.317910@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I am trying to use delivery_time to gauge the performance of my merge
agent.
In BOL this is defined as Number of seconds it took to apply a batch of
changes. In SQL Server 2000 this figure appears wrong.
I run the following select statement.
select start_time,time,delivery_time,comments
from MSmerge_history
where agent_id = 4
order by time desc
(Results shown at bottom.)
The question I have is this:
Between histrory entries the delivery_time which I can only assume is
cummulative like the rest of the metrics (e.g. insert count, duration
e.t.c) jump a very large amount, even though only a small amount of
time has passed.
Take the last 2 entries below. (I know these happened close together)
Delivery time is 150901 and 146479 respectively and the logged time is
09:18:45.753 and 09:18:45.550.
A difference of 4422 seconds???
If my assumption that delivery_time is a cumulative count in seconds is
correct than this value make no sense.
Either I am misunderstanding the data or this is just simply wrong.
Could it be milliseconds that might make sense?
start_time time delivery_time comments
2006-06-06 13:41:20.803 2006-06-07 09:18:45.753 150901 Downloaded 100
data changes (100 inserts, 0 updates, 0 deletes, 0 conflicts).
2006-06-06 13:41:20.803 2006-06-07 09:18:45.550 146479 Downloaded 102
data changes (102 inserts, 0 updates, 0 deletes, 0 conflicts).
2006-06-06 13:41:20.803 2006-06-07 09:18:45.080 142557 Downloaded 100
data changes (100 inserts, 0 updates, 0 deletes, 0 conflicts).
2006-06-06 13:41:20.803 2006-06-07 09:18:44.910 139198 Downloaded 100
data changes (100 inserts, 0 updates, 0 deletes, 0 conflicts).
2006-06-06 13:41:20.803 2006-06-07 09:18:37.033 135541 No data needed
to be merged.
2006-06-06 13:41:20.803 2006-06-07 09:17:36.940 135541 No data needed
to be merged.
.
- Follow-Ups:
- References:
- Prev by Date: MSmerge_history delivery_time seems wrong in 2000
- Next by Date: Re: sp_MSsub_check_identity performance
- Previous by thread: MSmerge_history delivery_time seems wrong in 2000
- Next by thread: Re: MSmerge_history delivery_time seems wrong in 2000
- Index(es):
Relevant Pages
|
|
