All Articles 21scripts-600x159

SQLBits 2019: Attention Pre-Con Attendees – One Free Consulting Hour

SQLBits 2019 is one of my most favorite events. 

If you are going to go to SQLBits 2019, you want to come to my pre-con about 21 Essential Scripts: Performance Tuning for EVERYONE. This pre-con contains best of my material and goes beyond what you conventionally know about any topic. It is no-nonsense, direct to demonstration and fast-paced advanced class where we discuss 21 essential scripts for SQL Server Performance Tuning.

Read More
All Articles optimizeperf-600x221

SQL SERVER – How to Optimize Your Server Performance by Reducing IO Waits?

SQL Server performance tuning is often considered as a complex subject and many DBAs and Developers often sees SQL Server Engines as a black box. However, the reality is very different as SQL Server Performance tuning is often a simple art of balancing three of the important resources for any system – 1) CPU, 2) Memory and 3) IO. In this blog post, we will discuss how we can reduce critical waits for queries and optimize server performance.

Read More
All Articles SQL-Server-Performance-Tuning-Practical-Workshop-600x120

SQL Server Performance Tuning Practical Workshop – Relaunched

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.

Read More
All Articles cloudwitness-tls-01-600x159

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

Read More