Comments
3 comments
-
Hi Matt,
I get a very similar thing happening when I attach a debugger to SQL Server Management Studio, and this is regardless of whether SQL Prompt 3 is running or not. CPU usage sits at 100% for ages. It does eventually come back but takes several minutes. As I understand it this behaviour is caused by the "fix" for a race condition that occurs within Management Studio, which can be triggered by a wide variety of things, but generally occurs if something takes more than 5 - 10 seconds. Then SSMS goes into this bizarre state where it just keeps trying to repaint itself. It's very irritating and I'm hoping it will be fixed in the upcoming SP2 as I've nearly torn all my hair out on multiple occasions because of it. I've also noticed that it can occur if you switch from SSMS to another window and back again whilst SSMS is starting up.
So, although it sounds like a cop out, it's not actually SQL Prompt's fault and is entirely beyond our control. The best thing I can suggest is (i) don't switch windows when starting SSMS, and (ii) don't minimise SSMS unless you absolutely have to.
Sorry I can't be more help than that.
Thanks,
Bart -
Makes sense, thanks for the response!
-
No problem, sorry I can't offer any kind of solution.
Thanks,
Bart
Add comment
Please sign in to leave a comment.
Periodically in SQL Prompt 3.0 (this doesn't happen all of the time). One time I noticed it after coming back to management studio after a couple hours of inactivity and started opening long scripts and creating new scripts.
What happens is that CPU usage goes to 100% and is split between a process called csrss.exe (which apparently handles drawing graphics to the screen or something), and explorer.exe. This only happens when I bring Management Studio back up and one time it just kept the "SQL Prompt is indexing your database" message up for a very long time, I killed it after about 7-8 minutes of waiting. I actually Had to stop SQL Server and the computer returned to normal (explorer.exe and csrss.exe were no longer taking up 100% of cpu usage).
My question is that it appears SQL Prompt is the cause of this, i've been using SQL Prompt 3.0 for several days now and today this has happened several times, but did not experience this issue before.
Any ideas?