Troubleshoot High CPU with SQL Diagnostic Manager

by Feb 2, 2018

We recently had an issue where our primary database server was sustaining 100 % CPU utilization.  We were able to identify sqlservr.exe was responsible for 95%.  We could not identify a user process taking all of the CPU.  Eventually, we were able to determine a script to delete 2 million rows that was being replicated was the cause.  Unfortunately, it took many hours to find this.  My question, is there someplace in Diagnostic Manager that we could have looked to find the replication problem?  Hope this makes sense.