We have been able to deal with this issue *mostly*. By moving the deadlock priority we get deadlocks about twice per month rather than twice a day. What I’ve found to be more of the root cause for the deadlock is our disk sub system gets very slow once a day. During this time, all queries slow down dramatically increasing the chances for a deadlock. Best of luck resolving it. I don’t have much experience using merge replication so unfortunately can’t speak from much experience there.

Best,
Derek

Your article (Gracefully Handling Deadlocks) speaks directly to my issue. I am seeing that when I run my merge replication from a client I am getting locks on what appears to be the server processes or application interaction to the DB from the server. Usingyour methods have you been able to deal with these situations? I am concered because we are going live with a solution that I didn’t see this type of locking issue until close to the end and I am trying to figure out how to resolve it.

Thanks,

Mike