Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chechu
Starting Member
9 Posts |
 Posted - 2011-06-06 : 07:24:15
|
| Hi there,We are facing an issue in our Server which is running our DB Engines. SQL process monopolizes the CPU consuming 100% of it and causing it to crash.We tried using SQL Profiler to fetch some data which is causing this to crash but when we run it the CPU usage decreases to 15 - 30% and keeps running sightly until we decide to stop it, when suddenly the CPU hits 100% and crashes.I've read a bit about this already, and I saw that Profiler disables the execution of sentences in order to allow the system to fetch data and when it closes, it "opens" the highway again... so this causes a big bottel neck.After all this explanation my questions are:1.- Any1 experienced someth similiar? If yes, how you solved this situation?2.- How I can get through Profiler so when I stop the sniff I void creating a bottle neck?Thanks in advance and best regards,Chechu. |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2011-06-06 : 07:42:09
|
| I've seen it with sharepoint - are you using that?Try running sp_who2 while cpu is 100% and see if you can find the culprit.==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
chechu
Starting Member
9 Posts |
Posted - 2011-06-06 : 09:52:50
|
| Hi there,Thanks for your reply.We are not running sharepoint, so it has nothing to do with that :/Anyone else have met this?I'll try to run the sp_who2 tho. As soon as I have the output i'll come back here.Regards,Chechu. |
|
|
|
|
|
|
SQL Profiler