I'm setting up a merge replication web publication for a table that needs to use the DateTime (Later Wins) conflict resolver so that the most recently modified row wins in any conflict. This table (and hundreds of other tables) use a datetimeoffset for their modified date as subscribers can be in many timezones. In order to get the required datetime value as a column I've added a ModifiedDateUTC datetime computed column which does a simple CONVERT to a datetime. The issue I'm seeing is that even though the article setup accepts this as a valid column, whenever I generate a conflict I get the error 'The specified conflict resolution column 'ModifiedDateUTC' could not be found.'

migrated from serverfault.com Apr 16 '18 at 12:01

This question came from our site for system and network administrators.

  • There should not be a confligt - this computed column should not be replicated at all. – TomTom Apr 11 '18 at 16:00
  • If the computed column is not replicated, then it doesn't make it to the subscriber. I'm intentionally generating conflicts (in other columns) to verify the resolver is working as intended. – Jason Apr 11 '18 at 16:13
  • But it still akes no sense because it can be reliably computed on the subscriber. – TomTom Apr 11 '18 at 16:18
  • The resolver runs at the publisher (supposedly by IIS) in web based merge replication. But you're right that it makes no sense, the computed column shows up in the conflict table without an issue,and is available at both the subscriber and the publisher. It should just be an easy comparison to decide which row wins. – Jason Apr 11 '18 at 16:19
  • Did you ever think there might be too many sub.stackexchange sites? ugh. – Jason Apr 11 '18 at 16:27

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.