Even if you are a DBA, sometime you need to deal with issues which are not related to SQL Server. It is not by design, but this is part of our job description. It is always interesting to troubleshoot such issues and find a solution. I always think, sharing such strange troubleshooting – it will help those who get into this problem, not understanding what is happening behind the scenes. Let us learn about in this module Windows Server 2008 R2 Failover Cluster.
SQL SERVER – Attaching and Restoring Database in Clustering Generates An Error – Notes from the Field #115
[Notes from Pinal]: In my career, I have seen many database experts who are great with what they do, but when they have to work with clustering or AlwaysOn solutions, they usually avoid it. The reason is that there are not many experts who know this subject well enough. One thing I always personally felt that the documentation is also not widely available when it is about clustering. If one receives some error, they are usually lost. This is when I reached out to Eduardo and asked him what can we do to if we face error while attaching or restoring database in clustering environment in SQL Server.
Here is the situation which my client explained and I was asked for help about SQL Cluster Resource.
We are having 2 node windows cluster having 3 SQL Server instances clustered running on Windows 2012 R2 on VMware. We have one instance that will start from the services.msc but not from the Failover Cluster Manager when attempting to bring the service online. In reality the services start because during the ‘Online pending’ I am able to connect and query the databases on that instance, although it is in the ‘Online pending’ state.
Do you know what could be the problem?