February 29, 2020 at 6:52 pm
Last week, I ran into two merge replication related issues:
For non-production, it's SQL 2016 to SQL 2016 merge replication, one schema change(a new column) was unable to replicate from publisher to subscriber. I had to reinitialize the subscriber with a new snapshot to get the replication article in sync.
On production, it's SQL 2016 to SQL 2008 merge replication, one row was changed on subscriber, but failed to replicate to the publisher. I made another change on that row, then it's replicated to publisher without any issue.
Anyone ran into similar issues? I didn't have any issues from 2013 to 2019. This occurred only after distributor/publisher was upgraded to SQL 2016 from SQL 2008R2. Not sure if it's Microsoft product bug or I should contact MS product support, I won't be able to reproduce the issue for sure.
March 1, 2020 at 7:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
March 5, 2020 at 2:04 pm
Replication will allow you to go only two version UP or DOWN
March 5, 2020 at 2:28 pm
Your statement("Replication will allow you to go only two version UP or DOWN") is for transactional replication only. I mentioned it's Merge Replication, no such restriction on merge replication.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply