如何检查合并复制是否真的完成 [英] How to check if Merge Replication is really complete or not

查看:42
本文介绍了如何检查合并复制是否真的完成的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

希望一些 SQL 复制天才可以帮助解决这个问题.

Hopefully some SQL replication genius can help on this one.

我们有一些手持设备在我们的 SQL 2008 R2 数据库上使用合并复制来保持本地数据库同步.

We've got some handheld devices that are using merge replication on our SQL 2008 R2 database to keep their local database in synch.

这在大多数情况下都有效,但客户端正在请求一份报告,显示同步进行时的状态.

This works most of the time but the client is requesting a report that shows the status of the synch as it progresses.

现在我在合并过程中查看 msmerge_history 和 msmerge_session 表,我注意到它们在设备本身完成之前很久就状态完成了.

Now I'm watching the msmerge_history and msmerge_session tables during the merge and I'm noticing that they state complete long before the device itself has completed.

因此,客户端看到同步已成功,但由于某种原因,它在 5 分钟后失败.

So the client is seeing that a synch has been successful only for it to fail 5 minutes later due to one reason or another.

如何查看客户端何时完成合并?

How can I see when the client has finished it's merge?

推荐答案

这并不完全是一个答案,但 Microsoft 已向我们确认我们无法从服务器实时监控订阅者进度.只能从订阅者那里进行监控.

It's not exactly an answer but Microsoft has confirmed to us that we can't monitor subscriber progress in real time from the server. It can only be monitored from the subscriber.

因此,我们将不得不改变订阅者的工作方式,以将其进度通知服务器.

So we are going to have to change the way our subscriber works to notify the server of it's progress.

这篇关于如何检查合并复制是否真的完成的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆