"Roy" <Roy@discussions.microsoft.com> wrote in message
news:A96295C7-71C5-4764-9093-6737DED1E033@microsoft.com...
> Hi
>
> We have configured merge replication in SQL 2005 (SP 1) for a database
> having more than 100 GB. The merge agent duration was for every 5 mins.
> Normally it used to take around 2 to 3 mins to complete. It was working
> fine
> till now but now it is taking around 45 minutes. When checked and viewed
> details in the replication monitor the below message was displayed for a
> long
> time.
>
> The process is waiting for a response from the query '{call
> sys.sp_MSenumchangesdirect(?,?,?,?,?,?,?,?,90,1,0,'39B06489-B2C7-4FA4-B109-8609CD6C18FF')}'
>
> Any help in this regard is appreciated
>
> Thanks.

"Hilary Cotter" <hilary.cotter@gmail.com> wrote in message
news:ugqNAvvEHHA.3820@TK2MSFTNGP02.phx.gbl...
> Are you using join Filters? Also you might want to drop your retention
> period so that metadata is purged more frequently.
>
> --
> 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
>
>
>
> "Roy" <Roy@discussions.microsoft.com> wrote in message
> news:A96295C7-71C5-4764-9093-6737DED1E033@microsoft.com...
>> Hi
>>
>> We have configured merge replication in SQL 2005 (SP 1) for a database
>> having more than 100 GB. The merge agent duration was for every 5 mins.
>> Normally it used to take around 2 to 3 mins to complete. It was working
>> fine
>> till now but now it is taking around 45 minutes. When checked and viewed
>> details in the replication monitor the below message was displayed for a
>> long
>> time.
>>
>> The process is waiting for a response from the query '{call
>> sys.sp_MSenumchangesdirect(?,?,?,?,?,?,?,?,90,1,0,'39B06489-B2C7-4FA4-B109-8609CD6C18FF')}'
>>
>> Any help in this regard is appreciated
>>
>> Thanks.
>
>