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. Join them; it only takes a minute:

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 have been having a recurring issue with transactional replication setups at the firm I work for. We use SQL 2008 R2. Seemingly without warning or any replication errors, all of the msrepl_tran_version columns (or nearly all of them) get out-of-sync between the two locations in a given setup.

I look in replication monitor and don't see any errors, and it's not as though the data changed for all the rows. Instead, most of the data remains identical between the two instances, but as users make changes at one location they don't update at the other due to the msrepl_tran_version columns being out-of-sync.

This issue is extremely frustrating, because I can't tell what's causing it and it requires substantial resynchronization to fix. Does anyone know what causes this symptom? Otherwise, does anyone have any ideas on how I can look to diagnose the issue? I would appreciate any advice anyone can provide.


share|improve this question

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.