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

We have a two SQL Server instances that use merge replication to keep in sync.

There is a single table that potentially can add millions of rows in between syncronisations (which is a relative small interval).

This table has a compound primary key (which is also the clustered index).

Replication is currently unable to merge changes between the two database servers (the query times out).

Is there any potential pitfalls with merge replication in this scenario? Is there a performance problem related to the database schema?

share|improve this question

migrated from Feb 28 '12 at 22:17

This question came from our site for professional and enthusiast programmers.

For the timeout issue, you can increase the Query Timeout value in the merge agent.

See this Replication Merge Agent reference to specifics on the QueryTimeOut.

share|improve this answer

Your Answer


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