August 20, 2002 at 3:11 pm
I am serving up an ASP driven site that reports from my database...2-3 times during the day it will run the reports painfully slow and I notice that the SQLSERVR.EXE process is using over 50% of my CPU resources and about 392 MEG of memory. Has anyone experienced this before, can anyone shed any light on this issue. Thanks for the time.
Thanks For your continued Help.
Thanks For your continued Help.
August 20, 2002 at 4:01 pm
Memory usage isn't a big deal unless you're paging because you don't have enough. Even 50% cpu utilization isn't cause for alarm, when you're 75% or higher consistently or seeing long spikes to 100% is when it's really bad. No simple answer, you have to see why the load is increasing. Maybe batch jobs running? Users hitting the site at break/lunch? Out of the queries being run, which are taking the most resources? I'd start by running Perfmon to capture some counters and do some light profiling at the same time.
Andy
August 21, 2002 at 5:36 am
I will do that. I have started doing some perf checking on some of the SQL aspects. Hopefully I can establish a trend. Thanks for the help...Hey do you know of any decent 3rd party diag or perf mon tools out there. I see there is the netIQ has a diagnostic dashboard that your site is promoting. Do you recommend it?
Thanks again Andy-
Thanks For your continued Help.
Thanks For your continued Help.
August 21, 2002 at 6:19 am
I've tried most of them, none seemed quite what I wanted, but all have good points. Suggest starting with the built in stuff, get a feel for what it can/cant do, then look for 3rd party solutions.
Andy
August 22, 2002 at 4:05 am
I agree with Andy, many are intrusive or run intrusive processes which will add load to your server. If you have concerns over the usage you don't want to add to it. In addition to perf mon in Windows I would use Profiler to try and catch the worst performing queries that execute often. They may need to be rewritten and in doing so may lighten the load. Also if you have other processes than SQL running on the box the can be adding to the overall load. Finally, the place you should start is event viewer and SQL logs, recently encountered a process that was writting an error to the event viewer logs so often but was esentialy masked due to a relationship that had not been realized with the process that was being troubleshot.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply