Recently, I was trying to simulate a client’s environment for which I need to have windows cluster with cloud witness. It didn’t go well, and I encountered an error message. In this blog, I will share the solution of error – “The client and server cannot communicate, because they do not possess a common algorithm” which I received while adding cloud witness. I was following below documentation: Deploy a Cloud Witness for a Failover Cluster
SQL SERVER – FIX: Msg 41105: Failed to Create the Windows Server Failover Clustering (WSFC) Resource With Name and Type ‘SQL Server Availability Group’
Sometimes there are errors which give us the solution to the problem and I love to discover other ways to fix it. In this blog, we would learn how to fix Failed to create the Windows Server Failover Clustering (WSFC) resource with name and type ‘SQL Server Availability Group’
SQL SERVER – Which Settings Change in sp_configure Needs Restart to Take Effect?
Learning one new thing every day keeps me passionate about my job. Recently, I had a very interesting experience with one of my customer while working with them on Comprehensive Database Performance Health Check and found some non-default values in sp_configure. They asked me – Which settings change in sp_configure needs restart to take effect? Do we need to remember the values?
SQL SERVER – Installation Failure – Specified Instance Via Transform is Already Installed. MSINEWINSTANCE Requires a New Instance that is not Installed
This is one of the situations where my client installed one clustered instance of SQL Server and the second one was failing. In this blog, I would share my findings of error: Specified instance via transform is already installed. MSINEWINSTANCE requires a new instance that is not installed.
SQL SERVER – Cluster Install Failure – Code 0x84cf0003 – Updating Permission Setting for Folder Failed
There are various issues which I have seen SQL installation and most of the time they are intuitive. The error message is mostly helpful and provides the right direction. In this blog we would discuss error Updating permission setting for folder failed:
SQL SERVER – Cannot Shrink Log File Because Total Number of Logical Log Files
Since I wrote my article about the script of shrinking the Log Files, there have been many emails from my blog readers about various messages.
SQL SERVER – Information Message: Cannot shrink file in database to xxxx pages as it only contains yyyy pages.
I often get emails from my blog readers asking various types of clarifications about my own blog. Here is one of the interesting questions from a reader about message Cannot shrink file in the database to xxxx pages as it only contains yyyy pages which he encountered after following my below blog.