Last week, I worked on an issue which might sound weird or strange when you hear it for the first time. “Whenever we fail SQL Server AlwaysON Group from Cluster, Node A loses its network connectivity.” (Sounds weird, Right ???) Here is the email which I received from my customer We’re able to re-create the… Continue reading SQL Server AlwaysON Group Failover in Cluster causes Node to lose network connectivity
Consideration for changing the default port of default SQL instance on Multi-subnet Failover Cluster
Security Hardening or Security Audits in an enterprise are some of the motivation for DBAs to run SQL Server default instance on a non-default port. For standalone instances, there are no challenges in changing the default instance port to non-default port, however for clustered instance there are some considerations since cluster.exe performs IsAlive check by… Continue reading Consideration for changing the default port of default SQL instance on Multi-subnet Failover Cluster
Gotcha – Listening SQL Server Availability Group Listener on non-default port
While configuring SQL Server AlwaysON Availability Groups, as a part of security hardening practice it is recommended to configure Availability Group to listen on a non-default port other than 1433. However the moment you configure your Availability Group Listener on a non-default port and if you SQL Server instance is also configured to listen on… Continue reading Gotcha – Listening SQL Server Availability Group Listener on non-default port
When do we need asymmetric storage with AlwaysON FCI and Availability Storage?
Before we start the discussion on SQL 2012 AlwaysON let me define the terminologies introduced with SQL 2012. As we all know with SQL 2012, we have AlwaysON solution which provides us with a HADR Solution. SQL 2012 AlwaysON can be configured in 2 modes viz AlwaysON Failover Clustering Instance (FCI): This is the… Continue reading When do we need asymmetric storage with AlwaysON FCI and Availability Storage?
SQL Server 2012 AlwaysON Automatic Failover Set – Caveat
As I was going through the documentation of AlwaysON, I came across the following caveat with SQL Server AlwaysON Automatic Failover set. While we can have upto synchronous secondary replica, we can have only one secondary replica to be part of Automatic Failover Set. Now, what that means is only of the synchronous secondary replica… Continue reading SQL Server 2012 AlwaysON Automatic Failover Set – Caveat
Considerations for Configuring Log Shipping for a cross-domain clustered instance of SQL Server over a Firewall
Last week, one of my customers had engaged me for consulting to configure Log Shipping on clustered instance of SQL Servers which are running in different domains. In other words, the primary and secondary servers are in different domains. While Log Shipping is pretty easy to configure but configuring log-shipping for a cross-domain clustered instance… Continue reading Considerations for Configuring Log Shipping for a cross-domain clustered instance of SQL Server over a Firewall
Failed to join the instance to the availability group while configuring AlwaysON
As SQL 2012 is in it’s RC0 phase, I was trying to configure AlwaysON on my 2-node WSFC with node and disk majority.Next I installed Default instance of SQL Server in parallel ( to save some time ) on both nodes of the WSFC.Next I enabled my instances for AlwaysON from SQL Configuration Manager for… Continue reading Failed to join the instance to the availability group while configuring AlwaysON