Here is my SQL use case:
Customer has invested in P2P transactional replication in SQL Server 2008R. Their database has many unique and composite key constraints that is likely to cause merge conflicts.
- Is there a method to automagicly resolve conflicts (ie: merge replication business logic resolvers) when using P2P transactional replication
- Is Merge publishing a supported way to handle databases with a high potential for conflicts
- Is Merge publishing deprecated