SqlSyncProvider - 如何使用datetime作为跟踪方案，与逻辑时钟Timestamp相对 [英] SqlSyncProvider - How to use datetime as tracking scheme as oppose to logical clock Timestamp

问题描述

我注意到使用Timestamp作为跟踪模式会在需要处理的数据库备份和恢复方面遇到一些问题。

如何在SqlSyncProvider中使用datetime作为跟踪方案？
如果SqlSyncProvider不支持日期时间作为跟踪模式，那么任何使用同步框架2.0的代码都可以参考吗？

感谢

I notice that using Timestamp as a tracking schema would have some issues on database backup and restore that need to deal with.

How do i use datetime as tracking scheme in the SqlSyncProvider ?
If SqlSyncProvider  does not support datetime as tracking schema, any codes sample utilizing sync framework 2.0 which I can be referred on ?

thanks

推荐答案

SqlSyncProvider的好处是它大大减少了Sync解决方案编写者的工作量。
由此，SqlSyncProvider的配置使用预先准备的跟踪模式。

如果需要更改跟踪列类型，则需要更改所有相关的跟踪表，触发器，存储过程等。使用SqlSyncProvider并非完全不可能。但是，在该基础中，使用DbSyncProvider将是一个更自然的选择。

我们将研究备份/恢复问题，看看问题的根本原因以及解决方法。

谢谢。

The benefit of SqlSyncProvider is that it dramatically reduces the efforts put in by the Sync solution writer.
With that, the provisioning by SqlSyncProvider uses a pre-cooked tracking schema.

If the tracking column type needs to be changed, that will require changing all the related tracking table, triggers, stored procedures etc.
It's not entirely impossible with SqlSyncProvider. However, in that base, using DbSyncProvider would be a more natural option.

We will look into the backup/restore problem and see what's root cause of the problem and how to address it.

Thanks.

这篇关于SqlSyncProvider - 如何使用datetime作为跟踪方案，与逻辑时钟Timestamp相对的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！