除了 RESTORE DATABASE 之外，还有其他原因导致 Service Broker 被禁用吗
我们有一个生产数据库，其中服务代理被禁用。 我们有一个分析器来记录每个备份/恢复操作。我在其跟踪中找不到任何恢复操作。 除了禁用服务代理的数据库恢复之外，还有其他原因吗？
请注意，该数据库是使用高可用性和见证服务器进行镜像的。在错误日志中，我可以找到
2011-07-29 09:00:52.53 spid25s Error: 1479, Severity: 16, State: 2.
2011-07-29 09:00:52.53 spid25s The mirroring connection to "TCP://DB84200:5022" has timed out for database "XXX" after 10 seconds without a response. Check the service and network connections.
2011-07-29 09:00:53.05 spid24s Database mirroring is inactive for database 'XXX'. This is an informational message only. No user action is required.
2011-07-29 09:00:53.72 spid24s Error: 1404, Severity: 16, State: 6.
2011-07-29 09:00:53.72 spid24s The command failed because the database mirror is busy. Reissue the command later.
Can mirorring failure disable servicebroker ?或者也许情况恰恰相反：由于服务代理被禁用而导致镜像失败？
任何解决此问题的建议将不胜感激！
We have a production database where service broker was disabled.
We have a profiler that logs every backup / restore operation. I cannot find any restore operation in its trace.
Are there any other reasons than a database restore for service broker to be disabled ?
Note that this database is mirrored using high-availability and a witness server. In the error log, I can find
2011-07-29 09:00:52.53 spid25s Error: 1479, Severity: 16, State: 2.
2011-07-29 09:00:52.53 spid25s The mirroring connection to "TCP://DB84200:5022" has timed out for database "XXX" after 10 seconds without a response. Check the service and network connections.
2011-07-29 09:00:53.05 spid24s Database mirroring is inactive for database 'XXX'. This is an informational message only. No user action is required.
2011-07-29 09:00:53.72 spid24s Error: 1404, Severity: 16, State: 6.
2011-07-29 09:00:53.72 spid24s The command failed because the database mirror is busy. Reissue the command later.
Can mirorring failure disable service broker ? Or maybe is it the opposite : mirorring fails because service broker is disabled ?
Any suggestion to solve this issue would be greatly appreciated !
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Service Broker 提供自动有害消息检测。如果从队列接收消息的事务回滚五次，自动有害消息检测会将队列状态设置为 OFF。
检查 SQL Server 日志以了解回滚情况。
但这看起来更像是镜像错误。
Service Broker provides automatic poison message detection. Automatic poison message detection sets the queue status to OFF if a transaction that receives messages from the queue rolls back five times.
Check the SQL Server Logs for the roll backs.
This looks more like a mirroring error though.