September 15, 2009 at 12:16 pm
the screen shot is in the attachment:
using sp_who2 to see process to find out what is making the server run slow I see this.
1. If it is a Background process and the CPUTime is 28250, is it currently slowing things down or
just when something comes in for it to monitor.
2. Is it on by default, where can i and should i stop it from running. a check box somewhere
3. In General what is the best thing to look for when all the sudden everyone is complining about sql server running slow other than
rebuiling indexes, related to what processes stand out that can and should be killed
September 15, 2009 at 12:27 pm
Hmm..
You may want to look into next performance degrading areas:
- Locking/blocking issues as a result massive select, insert, update, delete operation
- Tempdb files space issue
- Database log file size issue
- Memory issue
- CPU issue
All of them can degrade server performance significantly.
September 15, 2009 at 1:05 pm
I would be ultra careful about killing and SPID with a value less than 50, they tend to be system processes. I think you need to be looking elsewhere for your problem.
Have you looked at your query plans lately?
CEWII
September 15, 2009 at 4:22 pm
This article and the contained T-SQL statement may help you identify what T-SQL may be creating your problem.
What SQL Statements Are Currently Executing? By Ian Stirk, 2008/10/28
link:
http://www.sqlservercentral.com/articles/DMV/64425/
Be sure to read the comments posted about the article as well.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply