标准自定义提供程序 - 使用目标同步知识枚举更改 [英] Standard custom provider - Enumerating changes using destination sync knowledge

问题描述

 如果已经询问并回答了这个问题，我会提前道歉。

 I apologize in advance if this question has been asked and answered.

我正在努力实施使用标准自定义提供程序同步。作为第一步之一，源提供程序必须根据目标提供程序的SyncKnowledge在GetChangeBatch方法中提供更改。在我看过的样本和
文档中，方法似乎是：遍历商店中的所有商品，并检查每个商品是否包含在目标知识中。 

I am trying to implement sync using a standard custom provider. As one of the first steps, the source provider has to provide the changes in the GetChangeBatch method based on the destination provider's SyncKnowledge. In the samples I have seen and in the documentation, the approach seems to be: iterate through all items in the store and check if each is contained in the destination knowledge. 

当项目存储是一个小集合时，这是正常的，但是每次启动同步会话时都会遍历项目存储，当项目存储可能包含大项目时，在生产环境中似乎没有意义（和增长）
项目的数量。你能指点我更实际的GetChangeBatch实现吗？我是否完全错了？

This is ok when the item store is a small collection, but iterating through the item store every time when a sync sessions is initiated, doesn't seem to make sense in a Production environment when the item store may contain a large (and growing) number of items. Can you point me to a more real-world implementation of GetChangeBatch ? Am I getting this completely wrong?

在其中一个帮助主题中，我看到了这个注释：  更改枚举也可以使用直接处理查询商品商店或使用查询和此算法的组合，如果项目商店支持

In one of the help topics, I see this note: Change enumeration can also be handled by using either a direct query on the item store or by using a combination of a query and this algorithm, if it is supported by the item store

这是什么我想这样做，即使用（映射的）目的地知识中的信息在我的商店商店上运行查询，以获得更改。  你能指点我吗？例如，或提供指导？

谢谢和问候，

推荐答案

有你尝试使用FindMinTickCountForReplica并将该值用作下限值或开始枚举商店中的更改，以便您不通过所有项目？

have you tried using the FindMinTickCountForReplica and use that value as the lower bound value or starting point for enumerating changes in the store so you dont go thru all items?

这篇关于标准自定义提供程序 - 使用目标同步知识枚举更改的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！