在源对等方上插入新行不会在目标对等方上同步 [英] Inserting New Row on Source Peer Does Not Sync on Destination Peer

问题描述

我有一个示例应用程序，它是一个SQL Server点对点单向同步应用程序，看起来工作正常，除了当我在Souce Peer上插入新记录并同步时，记录是没有插入我的目标同行，我无法弄清楚为什么。我看到跟踪表中显示的
记录与初始同步中的初始插入记录不同：

scope_update_peer_key = 0  ，1为所有其他eecords

scope_create_peer_key = 0

和

sync_row_is_tombstone = 1

 

我假设墓碑设置与它有关，但我无法弄清楚是什么。我正在运行的代码示例是SqlSyncProvider简单提供程序示例应用程序。有谁知道这是否应该如何工作以及我需要做什么来
确保在我的Source Peer中添加的任何记录并且在任何后续同步中始终添加到我的目标对等点？

谢谢

解决方案

如果您使用非时间戳方式跟踪数据库同步提供程序的更改，则不支持。请查看此帖：  http：// social .msdn.microsoft.com /论坛/ EN-US / syncdevdiscussions /线程/ 66962f7c-efee-49d0-b927-b1ef36300bab 。

I have a sample app that is a SQL Server peer-to-peer one-way sync app that seesm to be working fine except that when I insert a new record on the Souce Peer and sync, the record is not inserted on my Destination peer and I can't figure out why. I see a record appear in my tracking table that differs from the initially inserted records from the initial sync by:

scope_update_peer_key=0  , 1 for all other eecords

scope_create_peer_key=0

and

sync_row_is_tombstone=1

 

I am assuming the tombstone setting has something to do with it, but I can't figure out what. The code sample I am running is the SqlSyncProvider simple provider sample app. Does anyone know if this is how this is supposed to work and what I need to do to insure that any records added at my Source Peer and always added to my Destination peer on any successive syncs?

Thanks

解决方案

If you are using non-timestamp way to track changes for DB Sync provider, this is not supported. please check this post:  http://social.msdn.microsoft.com/Forums/en-US/syncdevdiscussions/thread/66962f7c-efee-49d0-b927-b1ef36300bab.

这篇关于在源对等方上插入新行不会在目标对等方上同步的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！