大规模合并复制策略 - 可能会出现什么问题？
我正在开发一款在 Windows Mobile 6 上使用合并复制和 SQL Compact 的软件。目前它在 5 台设备上运行得相当好。
我遇到的问题如下：
架构必须进行很大的更改，并且随着应用程序的发展将继续进行更改。将这些架构更改复制到设备时出现各种错误，由于架构不一致导致上传失败。
订阅到期（14 天后）并且无法通过上传重新初始化 - 又称为，截至该点未同步数据的潜在数据丢失。
基本上，最坏的情况是数据丢失，当合并复制失败时，似乎没有办法恢复数据。到目前为止，我的方法是在设备上删除并创建订阅。我没有听到很多人这样做，尽管它似乎解决了所有问题。
长期计划是将其推广到 500 多台设备。对于从事类似项目的人员以及如何最大程度地减少数据丢失并使其有适当的错误处理代码从同步失败中恢复的任何建议，我们将不胜感激。
I'm developing a piece of software that uses Merge Replication and SQL Compact on Windows Mobile 6. At the moment it is running on 5 devices reasonably well.
The issues I've come up against are as follows:
The schema has had to change a lot, and will continue to have to change as the application evolves. There have been various errors replicating these schema changes down to the device, uploads failing due to schema inconsistencies.
Subscriptions expiring (after 14 days) and unable to reinitialize with upload - AKA, potential data los of unsynced data up to that point.
Basically, the worst case scenario is data loss, and when merge replication fails, there seems to be no way back to get the data off. My method until now has been to drop and create the subscription on the device. I don't hear many people doing this, though it seems to solve everything.
The long term plan is to role this out to 500+ devices. Any advice on people who have undertaken similar projects, and how to minimise data loss and make it so that there's appropriate error handling code to recover from sync failures would be much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
从脚本重建复制似乎是一项相当简单的任务，直到您开始遇到数据不一致问题，然后必须手动更正数据才能同步数据。
我建议您研究 ADO.Net 的同步服务而不是复制。
http://msdn.microsoft.com/en-us/sync/bb887608。 ASPX
Rebuilding replication from a script seems a fairly straightforward task until you start getting into data inconsistencies and then have to manually correct data before it can be synchronized.
I would suggest you look into Sync Services for ADO.Net rather than replication.
http://msdn.microsoft.com/en-us/sync/bb887608.aspx
建议您看看 Rob Tiffany 的书，其中包含有关扩展到许多用户的建议。为了在订阅过期时保存数据，您可以实现一个 Web 服务来上传 sdf，然后通过使用一个小型实用程序来执行设备数据库中的任何插入/更新/删除操作。
Suggest you look at Rob Tiffany's book, it is packed with advice for scaling to many users. In order to save data when a subscription expires, you can implement a web service to upload the sdf and then apply any inserts/updates/deletes from the device database by manking a small utitlty to do that.
我们使用名为 Utility Center 的应用程序已有大约 7 年的时间，该应用程序使用 SQL Server 合并复制。目前我们在 120 台机器上拥有该应用程序。我们经常遇到数据无法到达订阅者的问题，但这并不会使软件无法使用。该软件还安装在笔记本电脑等上，人们可以带回家关机等。此外，有些人进行无线同步，这也有其自身的问题。
We hace been using an application called Utility Center for about 7 years that uses SQL server merge replication. Currently we have the application on 120 machines. We are constantly having issues with data not getting to the subscribers but it does not render the software unusable. Also the software is installed on laptops etc that people take home shutdown etc. In addition some folks sync wirelessly which has its own set of issues.