If you are reading this blog regularly the name of Dominic Wirth may not be new for you. He has in the past sent some very interesting scripts for audit for our blog and I am including his new script in this blog which is about how to Get CPU and Memory Information with MAXDOP Guidelines.
One of the most popular questions I receive during my Comprehensive Database Performance Health Check is a difference between status in sp_who2 which discusses status as Running, Pending, Runnable, Suspended. Let us today understand them with regards to CPU.
How to Know When Memory Constraints are Negatively Impacting CPU in SQL Server? – Interview Question of the Week #216
Question: How to Know When Memory Constraints are Negatively Impacting CPU in SQL Server?
During my recent SQL Server Performance Tuning Practical Workshop, someone asked, how do they know what is the automatically configured max worker threads for their machine. This is a good question. Microsoft has already answered this question so we will follow their guidance.
Have you ever imagined how often SQL Server performance issues are actually caused by poor capacity planning? Sometimes a SQL Server database has insufficient storage performance, an instance is running out of memory, or the server level CPU is skyrocketing to an unhealthy level.
Every consulting engagement is different and I enjoy interacting with different people while I am working with different experts. Earlier this week, here is what I heard during one of the Comprehensive Database Performance Health Check engagement about Parallelism for Heap Scan.