September 18, 2002 at 2:03 pm
I have a SQL 2K server that is being used by about 30 clients and at certain times, the CPU goes through the use. Need to know how I can track down what or who is causing that. Any suggestions?
About the same time every day, my SQL server gets really busy and my clients get real slow connectings. I'm monitoring what I know to monitor, Memory, Hard Drives, Processor and two SQL items. Got that from;
http://www.sql-server-performance.com/sql_server_performance_audit.asp
(good site)
At this point, I'd really appreciate any ideas. This is realy driving me nuts.
September 18, 2002 at 2:31 pm
I think I'd also begin profiling to see what is happening. Start with a general trace for a day or two, look for the heavy hitters. After that you might want to filter it down some, on duration or cpu usage maybe. What you have for counters is a decent start.
Andy
September 18, 2002 at 2:34 pm
You can limit profiler to queries with some long time (> 2 minutes or something) which will make it easier to track them down.
Steve Jones
September 18, 2002 at 2:50 pm
Both sound like a good idea. So, for someone who is rather green with SQL, which events, data columns, and filter would you all recommend for this trace?
September 19, 2002 at 1:32 am
Are you running any DBCC commands or backups during the specific times your server is slow for the users?
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
September 19, 2002 at 6:35 am
I don't have any backups running. What are DBCC commands?
September 19, 2002 at 7:35 am
quote:
What are DBCC commands?
DBCC CHECKDB for instance checks your database for allocation and consistency errors.
Are you running any scheduled job (maintenance plans for instance) during the slow periods?
Chris Hedgate @ Apptus Technologies (http://www.apptus.se)
September 30, 2002 at 6:54 am
It turns out that my problem with my SQL Server was not, at least directly, related to SQL. I have another server connected to it that was having problems with a frame relay connection. The connection was delaying causing that server to work extra hard to keep the connection up. We ended up changing some configurations to allow for the delay and, almost like magic, my SQL Server settled down.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply