This was another interesting situation where client reported that their SQL Server Cluster resource, sometimes, fail to come online when they perform failover of SQL Server from one node to another. In this blog, we would learn how to fix ” SQL Server resource not coming to an online state ” issue.
SQL SERVER – SharePoint not Working After Failover to Another Node
Anything that can go wrong will go wrong while Murphy is out of town. While I was onsite to help a client, one such issue had cropped up in their SharePoint environment where SQL Server was used as backend and was a part of Windows failover cluster. When SQL Server was failed over from Active to the Passive node, users were not able to connect to SharePoint site and they were not able to open any SharePoint page. Since it was critical for their business, I got engaged to provide suggestions.
SQL SERVER – Unable to Start SQL After Patching – Database SSISDB is Enabled for Database Mirroring
I do apply patches to my SQL instances as and when they are released by Microsoft. This is important because I always feel keeping the bits up-to-date is essential because I don’t want to get infected as I travel quite a bit. Since I play a lot with my SQL Server, there are more chances that things are going to break sooner than your production server. Here is one such incident. Let us learn about how to fix script level upgrade. Let us learn how to fix the error related to SSISDB.
SQL SERVER – Steps to Deploy Distributed Availability Group – Windows Clusters in Different Domains
In the current era where companies’ mergers and take over is a common phenomenon, it is possible to run into a situation where there are two domains which are connected but not trusted. I was engaged in consulting for a client who had a similar merger in the past. The reporting application was in a different domain and they wanted data to be synchronized in SQL Server database on parent domain. Essentially, they had two windows clusters and they want to have one AG across them. The only solution which came to my mind was Distributed Availability Group in SQL Server. To make things little more complicated, they did not want to use certificates to configure this setup. As per them, certificates will add an overhead of maintenance. Here is the oversimplified diagram of their deployment.
SQL SERVER – Event ID 1069 – Unable to Failover Clustered Instance to Another Node. Resource is not Loaded
While playing with my lab cluster, I ran into a situation. In this blog, we would learn about a situation where failover was not working from one node to another node. Everything used to work fine on Node1. Let us fix the error related to failover clustered.
SQL SERVER – Unable to Add Node – Could not find subkey System \ CurrentControlSet \ Services \ MSSQLFDLauncher. Error code 0x851B0001
After a bit of testing on my lab server, I was able to reproduce the issue! We will not see a feature listed on the Features Page if the respective MSI file is missing from the Setup Media. Full-Text Search using the MSI called sql_fulltext.msi and is present in the setup path MediaRoot\x64\Setup. I was not able to see the sql_fulltext.msi file in the client’s setup media. I was suspecting other files to be missing too so we extracted a fresh copy of the setup media (from new downloaded ISO) and then ran the “New Failover Cluster” setup. This time, we were able to see Full-Text Search option. Let us learn how to fix the error related to unable to add node.
SQL SERVER – Error: 1067 – Unable to Bring Analysis Service Online in Cluster
Even after working with many clients on various issues (Always On, Deployment, Performance Tuning) I always get new challenges as a part of my freelancing job. One thing I have learned is that one needs a systematic approach to diagnose the issue and, of course, passion to solve the problem. In this blog, we would learn about how to fix the error: 1067 which comes while trying to bring Analysis Service online in the cluster.