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
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?
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
We have observed a number of issue now where in clustered instance of sql server 2005 fails to come online after performing changing on shared disk on a cluster. As mentioned in my previous posts if the sql server fails to come online we need to start troubleshooting by looking at the sql server error… Continue reading SQL SERVER 2005 RESOURCE FAILS TO COME ONLINE ON CLUSTER AFTER CHANGING THE SAN DRIVE TO ADD MORE DISK SPACE
We have observed a number of case where we use sql server replication on a clustered instance of sql server and when we try to failover from Node 1 to Node 2 the Log Reader agent may fail to start with the following error Error messages: The process could not execute ‘sp_MSpub_adjust_identity’ on… Continue reading Log Reader Agent Fails when the Sql server instance is failed over to Node 2