tag:blogger.com,1999:blog-7958569345934714789.post59481682338819482..comments2016-09-16T11:17:41.265-04:00Comments on Jeff Stevenson's Technology Blog: Identifying High CPU SQL Processesjxs2151http://www.blogger.com/profile/13599578258965424531noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-7958569345934714789.post-77979929962061012312013-08-02T14:01:17.970-04:002013-08-02T14:01:17.970-04:00We are in the process of implementing EnterpriseOn...We are in the process of implementing EnterpriseOne 9.1 in our company. <br /><br />These cursors and SQL statements are helpful, but I am in need of one more piece of information. I need to know the value of the "@" variables that are being used in the SQL statements. Is there a way to get this information?Jason Boyettenoreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-87469215067336796932013-02-05T17:47:33.854-05:002013-02-05T17:47:33.854-05:00One can indeed get the Thread ID from Process Expl...One can indeed get the Thread ID from Process Explorer by selecting the sqlservr.exe process and choosing Process/Properties, then the Threads tab. <br /><br />Using this method would allow you to skip the perfmon steps at the beginning and jump to the part where you determine the KPID to SPID relationship.Jeff Stevensonhttps://www.blogger.com/profile/08951573035924566608noreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-28835410114445588142012-12-27T20:15:26.379-05:002012-12-27T20:15:26.379-05:00use Sysinternal Process Explorer you will find Thr...use Sysinternal Process Explorer you will find Thread ID/KPID using high CPU right away.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-12543766573117774742012-10-12T14:19:49.149-04:002012-10-12T14:19:49.149-04:00Good article Jeff. One question: will saving the ...Good article Jeff. One question: will saving the msc settings for perfmon work when the Thread IDs will be different the next time you run this?Anonymoushttps://www.blogger.com/profile/10367091525204571644noreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-40903498964032232152011-07-28T22:04:44.347-04:002011-07-28T22:04:44.347-04:00Very cool, I have been looking for something like ...Very cool, I have been looking for something like this for a couple of years.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-13358609546954393122011-03-25T10:26:03.700-04:002011-03-25T10:26:03.700-04:00Thank you very much for this guide! It is an abso...Thank you very much for this guide! It is an absolutely great guide as I'm not a full time DB admin this was very easy to follow!<br /><br />lawson23Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-15562274971846420322009-12-14T08:32:37.456-05:002009-12-14T08:32:37.456-05:00Fantastic guide! I've been struggling with the...Fantastic guide! I've been struggling with the exact phone calls you are mentioning regarding our CRM system:) This is of great help!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-37915170078784519652009-09-14T08:40:09.430-04:002009-09-14T08:40:09.430-04:00I have been searching for a comprehensive guide to...I have been searching for a comprehensive guide to troubleshoot cpu spikes on a db server. This is the best one that I got and it practical.Unknownhttps://www.blogger.com/profile/07171245950731349048noreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-83611037867206067592009-06-07T14:26:25.720-04:002009-06-07T14:26:25.720-04:00Thanks Jeff.
Now instead of dreading the next tim...Thanks Jeff. <br />Now instead of dreading the next time my production server gets stuck on 100% cpu utilization, I'll look forward to it. ;)Amboy Observerhttps://www.blogger.com/profile/02364240920939457248noreply@blogger.comtag:blogger.com,1999:blog-7958569345934714789.post-67627225090062772152008-10-23T21:54:00.000-04:002008-10-23T21:54:00.000-04:00Thanks, this is useful!! Had a prod issue the othe...Thanks, this is useful!! Had a prod issue the other day and for some reason cpu usage on sql server was shooting way high and stayed constantly above 70% causing other application to hang and report not to run. There was no lock and couldn’t work out which pid was hitting hard on sql and was force to restart the sql instance to resolve which is a bit extreme. Now to use this info and try Anonymousnoreply@blogger.com