MSmerge_history table and Replication Monitor

I need a detail report likeReplication Monitor Screen in the sqlserver.I
create one with the sql above but msmerge_history table stores only 2 days
data.How can i find all merge datas for my report..
SELECT id, t1, t2, t3
FROM (SELECT session_id id, MIN(time) t1 , MAX(time) t2 ,
CONVERT(NVARCHAR, DATEDIFF(second,
MIN(time), MAX(time))) t3
FROM MSmerge_history
WHERE (agent_id IN
(SELECT DISTINCT agent_id
FROM
MSreplication_monitordata
WHERE (publication
= 'PCPC001')))
GROUP BY session_id) AS senk
Please Help..
increase you history retention period.
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"The_TOZ" <tunc@.te-mob.com> wrote in message
news:C28DE854-081A-49DB-9021-650C4A1E5F0A@.microsoft.com...
>I need a detail report likeReplication Monitor Screen in the sqlserver.I
>create one with the sql above but msmerge_history table stores only 2 days
>data.How can i find all merge datas for my report..
>
> SELECT id, t1, t2, t3
> FROM (SELECT session_id id, MIN(time) t1 , MAX(time) t2 ,
> CONVERT(NVARCHAR, DATEDIFF(second,
> MIN(time), MAX(time))) t3
> FROM MSmerge_history
> WHERE (agent_id IN
> (SELECT DISTINCT agent_id
> FROM
> MSreplication_monitordata
> WHERE (publication
> = 'PCPC001')))
> GROUP BY session_id) AS senk
>
> Please Help..
>
|||On Nov 7, 4:35 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> increase you history retention period.
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com"The_TOZ" <t...@.te-mob.com> wrote in message
> news:C28DE854-081A-49DB-9021-650C4A1E5F0A@.microsoft.com...
>
>
>
> - Show quoted text -
Be careful increasing the history retention period if performance is a
concern. What we have done is pushed all the data you need to a
seperate 'reporting' database and run our queries from there.
|||I've always found this to be minor. I am following up with you offline Greg.
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
"Greg J" <greg.judkins@.gmail.com> wrote in message
news:1194447561.970841.22870@.o80g2000hse.googlegro ups.com...
> On Nov 7, 4:35 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> Be careful increasing the history retention period if performance is a
> concern. What we have done is pushed all the data you need to a
> seperate 'reporting' database and run our queries from there.
>
sql