What is the best way to detemine the cause of Processor Utilization High with no Top Queries
I have a SQL Server that over a 15 hour period raised the Processor Utilization High alert 10 times. Each time the processor was pegged nearly the whole time at 100% and it lasted between 4 and 7 minutes; but, there were no Top Queries listed even when the Systems Processes tab showed sqlserver.exe as the high consumer. I see that setting Trace On is not advised unless there is a known issue; if I respond to the alert by turning Trace on in order to potentially capture the cause, that would make it worse wouldn't it? Where is a good place to look at how to do a post mortem analysis for this?
0 · Share on Twitter