Merge Replication is very slow

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Roy - 28 Nov 2006 10:20 GMT

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.

Reply to this Message

Hilary Cotter - 28 Nov 2006 14:46 GMT

Are you using join Filters? Also you might want to drop your retention
period so that metadata is purged more frequently.

Signature

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

> Hi
>
[quoted text clipped - 13 lines]
>
> Thanks.

Reply to this Message

Mahesh [MSFT] - 29 Nov 2006 02:23 GMT

In addition to Hilary's suggestions, look at if you really need all the data
at the subscribers. Does all data change at both places, if not utilize the
downloadonly articles. And when using filters, see if you can use any of the
filtering enhancements in SQL Server 2005.

Also was there a lot of activity on the database recently that is causing
this wait?

Hope that helps
--Mahesh

[ This posting is provided "as is" with no warranties and confers no
rights. ]

> Are you using join Filters? Also you might want to drop your retention
> period so that metadata is purged more frequently.
[quoted text clipped - 16 lines]
>>
>> Thanks.

Reply to this Message