SQL合并复制[同步] [英] SQL merge replication [Synchronization]

问题描述

您好，



我在SQL Server 2008 R2上设置了合并复制。自上次同步发生以来，哪些交换发布者和订阅者之间已更改的所有行。



这里是一个我想问你们的方案。当发布服务器和订阅服务器在具有相同主键但行GUID不同的表中有一行时会发生什么。订阅者中的行是较新的并且稍后创建。



这时当我同步时，服务器上的行被删除。这为什么会发生？任何合理的解释？



我知道服务器和客户端的行应该具有相同的GUID。



问候，

Saurabh

Hi there ,

I have set up a Merge replication on the SQL server 2008 R2 . Which exchanges all rows that have changed between the Publisher and Subscriber since the last time synchronization occurred.

here is one scenario i want to ask you guys about. What happens when the Publisher and Subscriber have a row in a table with same primary key but different Row GUID. The row in the subscriber is newer and created later.

Here when i syncronize the row at the server gets deleted. why should this happen ? any logical explanation?

i Know for fact that the rows at server and client should have the same GUID's.

With regards,
Saurabh

推荐答案

GUID应该是首要的关键。这将是使用它们的关键，您的客户端可以创建在与服务器同步时保持唯一的新行。

The GUID should be the primary key. That would be the point of using them, your clients can create new rows that remain unique when synched to the server.

这篇关于SQL合并复制[同步]的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！