Comments
Sort by recent activity
Since upgrading SQL Prompt, I've been running most of a week with code analysis turned on. I also noticed the initial hit from turning Code Analysis back on.
However, my machine has been up with scripts open for most of a week and no noticeable sluggishness yet. / comments
Since upgrading SQL Prompt, I've been running most of a week with code analysis turned on. I also noticed the initial hit from turning Code Analysis back on.
However, my machine has been up with s...
Thanks. I've been operating with Code Analysis turned on now for about a week and haven't discerned any sluggishness. However, it's too early to tell as I've had to reboot every day or two in the interim due to other issuese
How do I enable verbose logging? / comments
Thanks. I've been operating with Code Analysis turned on now for about a week and haven't discerned any sluggishness. However, it's too early to tell as I've had to reboot every day or two in the...
Cool. Got it. / comments
Cool. Got it.
As requested offline by Tianjiao Li, I have installed the latest version of SQL Prompt and the minor release. I am currently running 9.0.5.3501.
I appreciate the help towards clean code that the Code Analysis feature gives, and would really like to work with it turned on, if the excessive CPU usage could be resolved. It's interesting that I could work a couple days with Code Analysis turned on before the excessive CPU issues started.
I'll turn on Code Analysis again and see if the new build makes any difference. / comments
As requested offline by Tianjiao Li, I have installed the latest version of SQL Prompt and the minor release. I am currently running 9.0.5.3501.
I appreciate the help towards clean code that the C...
Tianjiao_Li:
Since my last posting (Dec 22nd), I have been running with Code Analysis turned off. I have not noticed any sluggishness since then. I have been away from my desk for extended times in the interim, however, due to the holidays, so I'll post an update toward the end of the week.
Thanks again for your help,
Jonathan / comments
Tianjiao_Li:
Since my last posting (Dec 22nd), I have been running with Code Analysis turned off. I have not noticed any sluggishness since then. I have been away from my desk for extended times ...
I downloaded Microsoft's ProcessExplorer and am running it. I don't see a huge CPU imprint (0.5 - 0.6). I do notice that the memory imprint of SSMS rose overnight from 840M to 970M. The sluggishness has started again, so I'm going to restart SSMS again (last / comments
I downloaded Microsoft's ProcessExplorer and am running it. I don't see a huge CPU imprint (0.5 - 0.6). I do notice that the memory imprint of SSMS rose overnight from 840M to 970M. The sluggish...
torsten.strauss: I just experienced SSMS going wild on the CPU usage (pegged at 25% on each of my 4 processors). This happened even though I had restarted SSMS this morning.
Tianjiao_Li: Thank you for getting back to me. Here's a first pass at answers:
I typically operate with 4-8 tabs open, sometimes more, but rarely. One of the tabs is always SQL Source Control. I also typically have the Object Explorer open.
I have turned off the Code Analysis functionality and will post back if the sluggishness continues.
So far, the places I've hit the sluggishness would not make sense absent the data in our database. The scripts are also typically sensitive enough that I don't want to upload them to a forum. Please advise further.
9.0.3.3299
/ comments
torsten.strauss: I just experienced SSMS going wild on the CPU usage (pegged at 25% on each of my 4 processors). This happened even though I had restarted SSMS this morning.
Tianjiao_Li: Thank you ...
Ok, I've installed the update. Thanks for the heads up! / comments
Ok, I've installed the update. Thanks for the heads up!
Cool! Thanks! / comments
Cool! Thanks!
I use Team Services and have had similar errors the last two days just clicking on the "commit changes" tab after applying changes from the "get latest." This morning I attempted to resolve the problem by unlinking/relinking but regretted doing so as I'm testing migration scripts on the beta RC.
Just now I got the message again, and went out to the "Caches" subfolder under "Transients" and deleted the whole folder (I had to go out of SSMS first). On reconnecting to SSMS the problem was no longer observed. / comments
I use Team Services and have had similar errors the last two days just clicking on the "commit changes" tab after applying changes from the "get latest." This morning I attempted to resolve the pr...