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 running merge replication with SQL 2012.

When I first create my publication the MSMerge_contents table is populated with a large number of records with the colv1 being set to 0xFF.

When I run the stored procedure like this,

sp_showcolv @colv =0xFF

It becomes apparent that these records do not represent actual changes to the underlying records, unless I am missing something?

Why are those records there? Is it because of partitioning, or column level tracking? I am using column level tracking, but am wondering whether I need to revisit this option?

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.