February 4, 2003 at 2:57 pm
I have recently set up Merge Replication over a WAN. I have noticed a significant amount of blocking occurring. Yesterday, merge was blocking OLTP users. It appeared it was having trouble keeping a network connection with the subscriber. Ultimately, I stopped and restarted the merge agent and it cleared up.
Today, the merge process was getting blocked by OLTP users in a significant fashion.
Any thoughts on what I can do to alleviate this blocking?
Remember this when a developer tells you it will just be temporary. Temporary = Permanent.
February 4, 2003 at 8:08 pm
I had a problem under SQL 7 where merge replication created the GUID column on the tables being replicated but did not create an index on that column. Without this column, the replication agent was causing a lot of table scans. These may be the cause of your problem.
If there is no index on the GUID column, simply create the index and the problem will disappear
Hope this helps
Cheers
Stephen
February 5, 2003 at 9:12 am
That was an interesting suggestion...thx. However, it appears there are indexes on the rowguid columns of these tables. Any other thoughts?
Remember this when a developer tells you it will just be temporary. Temporary = Permanent.
February 5, 2003 at 5:57 pm
Use profiler to look for long running queries. This should give you the SQL that is causing the problem. Once you have the SQL, check out the query plan for it - hopefully this will show what is going on
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply