|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Today @ 7:10 AM
Points: 485,
Visits: 1,568
|
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 4:02 PM
Points: 4,
Visits: 52
|
|
| Very good article. How about running the VBS file using windows Task scheduler. ?
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, December 03, 2010 8:07 AM
Points: 8,
Visits: 25
|
|
Hi, What actions do you perform if it reaches more than 90%. In my scenario, I have multiple SQL jobs which runs in while loop
e.g.
While(1=1) begin -- do something -- delete top 500 records from x table of SERVER A and insert into x table of SERVER B END
CPU usage of SERVER A reaches more than 90%. I know its because of infinite while loop but I have to transfer the record from server A to Server B as soon as records gets entered into SERVER A. Is there any way to deal with it.
Thanks, Satalaj.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 12:27 AM
Points: 483,
Visits: 1,191
|
|
Good article. Handy way to monitor CPU. But one improvement I would like to see is a way to find which process is causing the CPU hit. It may not be always SQL Server process. Or atleast it should say SQL usage % and other process usage %. Another improvement can be some information to figure out what internally caused the CPU pressure within SQL Server, if SQL was consuming the most of CPU. For addressing these, I prefer DMVs.
Regards, Raj
Strictlysql.blogspot.com
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, March 13, 2012 2:31 AM
Points: 12,
Visits: 44
|
|
What about @@CPU_BUSY and @@IO_BUSY
if you checked those two values e.g. every 10 seconds and the @CPU_BUSY had increased 8 seconds I would assume that it was running on 80%, that without the VBA and the security issues it imposes.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Wednesday, May 16, 2012 5:17 AM
Points: 11,
Visits: 23
|
|
Satalaj, you have to make sure that while running procedures in infinite loop, you make sure that you identify which procedures running parallely are getting the CPU usage up (by parallel, I mean the tasks running in parallel). Also, check the CXPACKETS running as the wait type.
You can also use SQL Server Profiler and also perfmon correlated together to toggle through the database and traces, to see when CPU usage creeps up.
Rgds!!
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 12:27 AM
Points: 483,
Visits: 1,191
|
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Today @ 7:10 AM
Points: 485,
Visits: 1,568
|
|
yes, that DMV will provide CPU info, however, those views are not available in SQL 2000. And unfortunately, like most of us, I still have quite a few SQL Server 2000 systems to look after.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Today @ 7:10 AM
Points: 485,
Visits: 1,568
|
|
hrc (11/17/2010) What about @@CPU_BUSY and @@IO_BUSY
if you checked those two values e.g. every 10 seconds and the @CPU_BUSY had increased 8 seconds I would assume that it was running on 80%, that without the VBA and the security issues it imposes.
might be possible, but i never found a good way to do that with either @@CPU_BUSY or sp_monitor. by using the Win32_PerfRawData_PerfOS_Processor object, the data is coming from the same place that perfmon uses. I find that to be highly accurate. Thanks
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, December 03, 2010 8:07 AM
Points: 8,
Visits: 25
|
|
yes, I know that query who leads high CPU utilisation. I had written that query in while loop. It simply deletes top 500 records with UPDlock,READPAST and insert them into linked SERVER B. Any suggestion?
|
|
|
|