In this blog post, we are going to discuss how to fix high CPU Consumption on SQL Server 2016 and SQL Server 2017. One of the large multinational corporations recently hired me for Comprehensive Database Performance Health Check. Usually, customer hires me once and we are able to fix all of their problems in very little time. However, this customer had a very unique scenario and I had to engage twice to help them out.
SQL SERVER 2016 – DBCC Command Enhancement with MAXDOP
When you want to be successful, you need to run alone and fast. But if you want to run longer, you want to run together. I have personally seen multiple instances where this statement holds true to every word. When working with customers and in various consulting engagements, I have seen it is not enough to just solve the problem. It is important to enable the team working on the project and make them aware of the reasons why it did happen in the first place. I always felt the art of working together will take us a long way. Even in performance engagements, I try to get the team involved as I go through the process of solving their problems. Let us learn in this blog post DBCC Command Enhancement with MAXDOP.
SQL SERVER – Query to Get CPU Usage History for SQL Server and Operating System
I have seen a number of customers manage their SQL Server environments in an adhoc manner. These accidental DBA’s need to know what happened in the system in a chronological order or even worst need to know what led to the lead up to a particular problem. Many times when we troubleshoot a problem with high CPU, its asked that when it all started and do we have any historical data of CPU usage? Here is the one query which I have re-written to have more details. Let us see Query to Get CPU Usage History for SQL Server and Operating System.
SQL SERVER – Discussion on understanding NUMA
SQL SERVER – Who is consuming CPU on my SQL Server?
SQL SERVER – Fix: SQL Server CPU Schedulers Offline
SQL SERVER – How to Find If Queries are Running in Parallel?
Let us learn today how to find if queries are running in Parallel? If a query runs in parallel it is a query that SQL Server thinks is expensive.