In the year 2017 just for an experiment, I decided to start a SQL Server Performance Tuning Practical Workshop. I had no idea, that I will be the biggest and most popular service delivered by SQLAuthority.com. Since the year 2017, I have been delivering one or two workshops every week.
When to Use sort_in_tempdb for Rebuilding Indexes? – Interview Question of the Week #207
Question: When to Use sort_in_tempdb for Rebuilding Indexes?
SQL SERVER – FIX: Cannot Connect to SQL in Azure Virtual Machine From Laptop
To keep up with the market trend, I have already done my hands-on with SQL in Azure Virtual Machine. In this blog, I would share my learning about a connectivity issue which I faced recently.
SQL SERVER – Unable to Set Cloud Witness. Error: The Client and Server Cannot Communicate, Because They do Not Possess a Common Algorithm
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 – Cannot Shrink Log File 2 (SQLAuthorityDB_log) Because the Logical Log File Located at the End of the File is in Use
Learning never stops for a consultant. In this blog, I would share another learning and discuss message: cannot shrink log file because the logical log file located at the end of the file is in use.
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?