Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using merge replication with SQL 2012.

When performing a clean sync using the merge agent I am getting a timeout on this stored procedure,


I am wondering what the best way to diagnose this issue? When I take the SQL that was run, and run it in management studio it runs instantly. I can only assume that part of the required operations were done the first time it was run and timed out.

More specifically it must be a particular group of merge articles that are slowing it down, so how can I isolate this?

share|improve this question
Have you looked through this: I know this is for SQL 2000, but since this stored procedure has been around since then I doubt troubleshooting it changed much with SQL 2012. – Shawn Melton Nov 26 '12 at 2:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.