December 16, 2015 at 3:02 pm
Hi,
Our environment has A-p clustering set up on 2 nodes. when failover occurs sql instance is not failovering to other node. We are getting service bus connections.
1) So we thought of removing cluster and setting always-on on 2 standalone boxes with mountpoint drives. But our application uses msdtc. Can we make our application, not to use msdtc services like disabling them and set always-on?
2) One more doubt, I know we cannot connect sql instance from passive node. But can we open ssms? I
December 17, 2015 at 6:10 am
gorripativ (12/16/2015)
Hi,Our environment has A-p clustering set up on 2 nodes. when failover occurs sql instance is not failovering to other node.
What errors were you getting?
What did you try to remediate them?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 17, 2015 at 2:13 pm
Perry Whittle (12/17/2015)
gorripativ (12/16/2015)
Hi,If we failover, drives are failing to other node. But ssms is not installed on other node.
Moreover we are getting service bus errors.
Our environment has A-p clustering set up on 2 nodes. when failover occurs sql instance is not failovering to other node.
What errors were you getting?
What did you try to remediate them?
December 18, 2015 at 7:51 am
???
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 19, 2015 at 4:34 pm
Just checking. Is your cluster set up correctly? Is SQL Server installed in cluster mode or SQL Server installed normally? Is SQL Server added to the second node?
Is MSDTC set up in cluster mode or locally?
Can you failover the SQL Server clustered application (or group, for Windows Server 2003) manually? Can you failover MSDTC cluster application manually?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply