Behaviour of Service Broker during clustered SQL Server failover

Hi,
I have 3 instances of SQL Server 2005 hosted on a 3-node cluster, using Polyserve clustering. Each instance is nominally hosted on its own node in the cluster.
I have configured Service Broker to route messages from INST-A (on NODE-1) to INST-C (on NODE-3), using TCP and a NetBIOS name. This NetBIOS name obviously uses the machine name of the node, rather than the virtual machine name of the instance.
Under normal conditions, this works, messages sent from INST-A to INST-C are received and processed.
However, should INST-C failover (for example to NODE-1), the route created to INST-C from INST-A is no longer valid; INST-C is now on a different node to that specified in the route.
Service Broker stops, unable to put messages onto the queue on INST-C, so backing them up in sys.transmission_queue on INST-A. To fix, I have to update the route as appropriate.
We have thousands of messages being sent every minute. While a delay in sending them during an actual failover is expected, would it not also be expected to recover itself and process any backlog without manual intervention?
Is there something I'm missing in my configuration? Or do I need to set up some other means to automatically update the route upon failover? In which case, how can I programmatically determine the node to which it has failed-over?
Configuration scripts:
Target Endpoint:
CREATE ENDPOINT ServiceBrokerTargetEndpoint
STATE = STARTED
AS TCP(LISTENER_PORT = xxxx)
FOR SERVICE_BROKER(AUTHENTICATION = WINDOWS, ENCRYPTION = REQUIRED)
CREATE ROUTE RouteToTargetService
WITH SERVICE_NAME = 'ServiceBrokerTargetService', ADDRESS = 'TCP://INST-C:xxxx'
INST-A and INST-C are both SQL 2005 Enterprise edition.
Thanks for any assistance.
Simon

Hi David,
Thanks for correctly guessing our longer term plans. It's good to know this won't be a problem in the future.
However, that doesn't answer my original question, which is a bit more pressing than waiting until we have migrated. If it can't be done, it can't be done, and we'll just bear that in mind when responding to failover events. But I would prefer
a definitive "no, it can't" rather than a speculative "no".
Regards,
Simon

Similar Messages

Can service broker work between SQL Server 2008 and 2012, ssbdiagnose returned an error !

Hello,
We have a setup of three applications that sends and receive messages using Service Broker.
One part is on a server, we'll call 'S' have Microsoft SQL Server 2008 (SP3) - 10.0.5512.0 (X64)
The other part, we'll call 'E' use to have Microsoft SQL Server 2008 (SP3) - 10.0.5512.0 (X64).
But I am migrating these apps to a new server, we'll call 'C' that has: Microsoft SQL Server 2012 (SP1) - 11.0.3339.0 (X64)
I have used this command line tool to test it :
ssbdiagnose -E CONFIGURATION FROM SERVICE "//E/S/CService" -S "ServerC" -d EDatabase TO SERVICE "//S/S/ECService" -S ServerS -d SDatabase ON CONTRACT //E/S/ECContact
It returned:
An internal exception occurred: Cannot read property ServiceBrokerGuid.
This property is not available on SQL Server 7.0.
So, I am wondering, is it supposed to work between these two versions ?
As more info, in the previous setup, it was using certificates but I have changed the Endpoints to use only Windows Authentication.
Thanks for any advice.
Claude

Hello,
Many thanks to you and Fanny for looking at my question.
In fact I was unclear, please let me provide you with more details.
Maybe the use of "always on" plays a role here... I will use different names so it might be clearer...
ServerSoftware2008 server has SoftwareDB database.
ServerEmployees2008 server has EmployeesDB database.
Service broker use to work fine between those two above, with certificates.
The new server comes in, two virtual servers with SQL Server 2012 Enterprise Edition with Always On.
I call it ServerEmployeesC but this is the listener. Behind, there is ServerEmployees2012_A and ServerEmployees2012_B and of course, both have a EmployeesDB database.
So, to use SSBDiagnose, I wonder if I need to use quotes around values and if I can use the listener name with FQDN. Concerning the use of instance name in the syntax, there is only one instance per server, is it best practice to use it on the command
line ?
Here is again, my command :
ssbdiagnose -E CONFIGURATION FROM SERVICE "//E/S/E" -S "ServerEmployeesC.sub.acme.com" -d EmployeesDB TO SERVICE "//S/S/E" -S "ServerSoftware2008.sub.acme.com" -d SoftwareDB ON CONTRACT //E/S/E
Again, many thanks for any help you will be able to provide, the people who configured this application at first are no longer here and I am trying to configure the new server in a task of migrating to SQL Server 2012 for one of the two servers involved
and I am having a lot of problems doing it.
Best regards,
Claude

Startup Setting of sql 2014 Clustered "SQL Server" Service

New cluster in testlab:
          Windows Server 2012 R2: N1, N2 (node 1, node 2)
          Sql Server 2014 installed on N1, N2
          Storage server (uses SMB share for Sql Data and Quorum).
N1 is active; N2 is passive. What is the proper setup for the SqlServer and SqlServerAgent
services on both boxes? (Should they be "manual" for both?)
TIA,
edm2
PS. I wonder if the startup setting option is used to implement the Active\passive state.

N1 is active; N2 is passive. What is the proper setup for the SqlServer and SqlServerAgent
services on both boxes? (Should they be "manual" for both?)
Hi edm,
In a two-node Windows Failover Cluster with SQL Server, one of the physical nodes is considered the active node, and the second one is the passive node for that single SQL Server instance. A single SQL Server instance can run on only a single node at a time;
and should a failover occur, the failed instance can failover to another node.
When we create a SQL Server Failover cluster, The startup type is set to manual for all cluster-aware services, including full-text search and SQL Server Agent, and cannot be changed during installation. Microsoft recommends that you configure service accounts
individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions.
For more information, you can review the following article.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/
Regards,
Sofiya Li
If you have any feedback on our support, please click
here.
Sofiya Li
TechNet Community Support

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Managed Service Accounts to run SQL Server Service

Has anyone played around with using managed service accounts for running the SQL Server Service? I am on a forest functional level of 2008R2 and was thinking about how cool it would be to use those for SQL Server. Unfortunately, I hear that it's not supported
by Microsoft and yet I've read about people doing that but would like to know if anyone has first hand experience. Otherwise, if not recommended, I'll stick to the old fashioned way of creating typical user accounts. Thanks in advance!

Hi Scott hi Sean
I see that my first answer was badly phrased.
Let me try to make it more clear:
Managed Service Accounts(MSA):
Works with Kerberos including Delegation, but:
NOT working with cluster nodes
NOT working for load balancing using Kerberos
More information:
http://blogs.technet.com/b/askds/archive/2009/09/10/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting.aspx
Group Managed Service Accounts (GMSA):
Works with Kerberos including Delegation, but:
NOT supported with Failover Clustered Instances
Here is the connect item:
http://connect.microsoft.com/SQLServer/feedback/details/767211/gmsa-for-sql-server-failover-clusters
@all Please feel free to vote(!). I am waiting for this as well.
This is the state of my information today. Feel free to correct me if you know of any changes.
Andreas Wolter (Blog |
Twitter)
MCM - Microsoft Certified Master SQL Server 2008
MCSM - Microsoft Certified Solutions Master Data Platform, SQL Server 2012
www.andreas-wolter.com |
www.SarpedonQualityLab.com

Disable Remote Resigtry service for SQL Server failover cluster

Hi,
Is it safe to disable Remote Registry service from the the two nodes of SQL Server failover clustering?
Operating system: Microsoft Server 2008 R2 Enterprise Edition (64-bit)
Database software: Microsoft SQL Server 2008 R2 Enterprise Edition (64-bit), Failover Clustering
Thank you.
Regards,
Gan

Hi Pradeep,
You are right. I tested and verified that the GUI of cluster (Failover Cluster Manager) was not working properly after disabling Remote Registry service. Thank you :)
Regards,
Gan

Can Reporting Services 2005 report on SQL Server 2012 database?

We would like to upgrade our SQL Server from Standard 2005 to Enterprise/Standard 2012. Unfortunately, we also have a lot of reports based on Reporting Services 2005. If possible we would like avoid upgrading them at this time.
Is it possible to run Reporting Services 2005 of SQL Server 2012? If yes then is there pre-requiste like drivers or dll or any other to connect SSRS 2005 to SQL server 2012?
If we run Reporting Services 2005 of SQL Server 2012 then do we will face performance lag issue due to version difference of SSRS 2005 and SQL server 2012?

Moderators,
Can anyone merge this -
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2c44351c-35b4-4208-a2b7-88fc810d53ff/can-reporting-services-2005-report-on-sql-server-2012-database?forum=sqlreportingservices
sathya - www.allaboutmssql.com ** Mark as answered if my post solved your problem and Vote as helpful if my post was useful **.

Activate Reporting Services on My Sharepoint SQL SERVER Databse ?

Hi,
I have small sharepoint farm (1 FW and 1 SQL).
I can't find if it's recommended or not to activate and use Reporting Services on the SHAREPOINT SQL SERVER Instance ?
I wouldn't want to decrease my global farm performance.
Thank you for helping.
Regards

SSRS integrated must run on a server that has SharePoint installed and joined to the farm. That will have a significant impact on the SQL Database Engine server from a memory contention and CPU utilization perspective.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Provide WCF service caller to a SQL server that is access by a technical user account

Hi,
we have a WCF Service that is hosted in a windows service and access a SQL Server database. The database is accessed with the technical user the windows service runs with. That means nevertheless of the WCF service caller, the database is always
accessed in context of the technical user. Furthermore some company users access the database via the SQL Management Studio and sign in via Windows Authentication.
The management now wants us to provide a change log functionality. In case data is changed by the WCF service the caller should be logged. In case of using the SQL Management Studio the domain-user's account should be logged.
Because both ways must be supported we want to use a table trigge to monitor insert/update/delete ddl events, but we got struggled by passing the WCF service caller to the SQL server database.
Does anyone have a good idea for the issue? Any advice is appreciated.
Kind regards,
Christian

Do you know a way to use the 'SET CONTEXT_INFO' expression wth LINQ2SQL?
This is a T-SQL forum. There are other forms for LINQ.
No, I don't know LINQ. Then again, why on earth would you? This would be a command you would submit when the WCF connects. Ah, of course, you are only connecting when you submit a query. Which you do through LINQ. Oh well. Could be an incitement to move
away from LINQ maybe? :-)
Erland Sommarskog, SQL Server MVP, [email protected]

When to user Availability Group versus traditional Clustered SQL Server

Hi...
I'm trying to get my arms around when to use an SQL Server 2014 Availability Group. Here are the characteristics about my platform:
2 physical servers (Windows Server 2012 / SQL Server 2014)
Both servers connected to same LAN
External SAN storage connected DIRECTLY to each physical server via fibr3-channel. (No fibre-channel switch)
Database resides on SAN storage.
I've set up a failover cluster between the 2 physical servers.
I've created a high availability group with a Primary/Secondary and synchronization.
Both Primary/Secondary are green and show synchronized. The concern I have is that the Primary says Synchronizing (No Data Loss) and the Secondary says Not Synchronizing (Data Loss). When I use the Failover Wizard to failover, it tells me that I will have
data loss on the Secondary.
So my questions are these, do you need more than one Secondary node to have an effective Availability Group? If I only plan to have the 2 physical servers, should I be setting up a traditional Clustered SQL Server installation.
I've used the traditional Clustered SQL Server in the past and used the Active/Passive licensing for the SQL Server software but the Always On Availability Group looked interesting to me, but NOT if it requires more than 2 physical servers and more
than 2 SQL Instances (and licenses) to provide proper failover capability.
All input will be appreciated.
Thanks,
Brett

Hi Brett,
An AlwaysOn Availability Group is created between several standalone SQL Server instances, you don’t need to set up a traditional clustered SQL Server installation when configuring AlwaysOn Availability Group. Also you can have an effective Availability Group
with only one Secondary node.
From your description, you have an synchronous-commit availability secondary replica
and it says Not Synchronizing. This issue can be caused by the following:
•The availability replica might be disconnected.
•The data movement might be suspended.
•The database might not be accessible.
•There might be a temporary delay issue due to network latency or the load on the primary or secondary replica.
Please resolve any connection or data movement suspend issues. You can check the events for this issue using SQL Server Management Studio, and find the database error.
Reference:
Data synchronization state of some availability database is not healthy
Availability databases in unhealthy data synchronization state (Error: 35285, Severity: 16, State: 1.)
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Service accounts rights in Sql Server 2008 clustered installation.

I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.

I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.
You should get Domain account created before starting cluster installation and specifically give these rights to the account.
Regarding rights below link might be helpful
http://blogs.msdn.com/b/askjay/archive/2011/02/28/required-rights-for-sql-server-service-account.aspx
When installing cluster make sure you use Domain account which is added as local administrator on both nodes.
It should have righst to create Computer name object(CNO) in domain where cluster is being created
Windows CNO must have complete rights on SQL server CNO.You should also take help from AD team in providing these rights and understanding if any.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Remote Desktop Services that require Native SQL Server Client in Windows Server 2012?

I have somehow gotten really confused on this.. Is the Remote Desktop Connection Broker the only Remote Desktop Service that requires the SQL Native Client to be installed in Windows Server 2012 (r2) ?

Hi,
If you plan on configuring RDCB in HA mode then the SQL native client is required. The other RDS role services do not require it.
-TP
Is High Availability Mode enabled by Default?

Behaviour of Service Broker during clustered SQL Server failover

Similar Messages

Maybe you are looking for