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.
During recent SQL Server Performance Tuning Practical Workshop I receive following question about Query Optimizer Fixes.
While doing performance tuning for one of my clients, I was looking at ERRORLOG files to understand about their system. I saw that trace flag 1117 and 1118 are enabled via startup parameter.
Last week I published below blog where I talked about a trace flag. Backup Randomly Failing with Error 112 (There is not enough space on the disk.) One of the reader commented, whether he needs to enable trace flag every time SQL Server is restarted?
I have been playing around with SQL Server 2016 for a while now and I have seemed to have learnt a number of interesting options when playing around with the new version. One of the readers after reading – SQL Server 2016 – Enhancements with TempDB asked me if the option of TraceFlags of 1117 and 1118 not available when working with user defined normal databases. This was a valid and appropriate question for sure. I was not sure where to start. Let us see traceflags related to AutoGrow and Mixed_Page_Allocations.