We have a merge replication between our three SQL servers at three different locations. One is the publisher and two are subscribers, and we have a primary key on a table (a unique field with is auto-incremental by one). On the publisher’s server, if the user creates a new order, the table assigns it a number (e.g. 1000 in the unique field). At the same time, a user enters a new order in the subscriber server, which is also assigned a number (e.g. 1000 in its unique field). When the merge replication takes place, though, the unique number has already been assigned on the publisher server and details for order no. 1000 will not be updated on the publisher (due to primary key constraints). How can we resolve this situation and allow both the subscriber and the publisher order number to be replicated without creating any conflicts?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!