简体繁体 English

（SQL Server）Service Broker和故障转移群集实例

[英](SQL Server) Service Broker and Failover Cluster Instance

原文 2018-02-28 17:12:52 6 1 sql-server/ service-broker/ failovercluster

Regarding a datawarehouse-like project, I am studying combination of SQL Server Service Broker in front of SQL Server Failover Cluster Instance, both hosted on a Windows Server Failover Cluster-ed double-node box. 关于类似数据仓库的项目，我正在研究SQL Server故障转移群集实例前面的SQL Server Service Broker组合，它们都托管在Windows Server故障转移群集双节点盒上。

My questions: 我的问题：

Is it really possible? 真的有可能吗？ :) :)
How will database service broker have to be declared to be compatible with a SQL FCI automatic failover behavior? 如何将数据库服务代理声明为与SQL FCI自动故障转移行为兼容？
Has the service broker to be declared on both "instance" nodes to be seen whichever the active node is? 是否在两个“实例”节点上都声明了服务代理，以便可以看到哪个活动节点？
In case I add a third read-only node to turn the thing into an Availability Group based on WSFC, how to make service broker and AG listener work together properly? 如果我添加了第三个只读节点，以将其转变为基于WSFC的可用性组，如何使服务代理和AG侦听器正常协作？

If I'm any wrong, please correct. 如果我有错，请更正。 Thanks a lot for sharing your expertise anyway. 非常感谢反正分享您的专业知识。

Jean-Yves 让·伊夫

PS: I know about both Change Data Capture/Change Tracking features to fit DWH needs, but I'd like to stick to SSB ;) PS：我知道两种更改数据捕获/更改跟踪功能都可以满足DWH的需求，但我想坚持使用SSB;）

1 个解决方案

Looks like specifying the virtual network name in the route shall do the trick. 看起来，在路由中指定虚拟网络名称就可以解决问题。 I am still a bit confused regarding the AG option, will see. 我会对AG选项感到有些困惑。 Thanks jyao/kirchner and Remus for the support 感谢jyao / kirchner和Remus的支持