Link to home
Start Free TrialLog in
Avatar of perksdev
perksdev

asked on

SQL Timeout errors

I keep getting SQL time out errors on a sql2000 data base not quite sure how to go about troubleshooting it.  

This seems to happen mostly when the transaction logs backup  hourly and when reports are run.  
Avatar of Jim P.
Jim P.
Flag of United States of America image

Hit the basic questions non this and we work from there:

Is the application timing out on the clients?

Is it a LAN or WAN?

Are you using TCP/IP or do you have named pipes running?

How much memory on the server? CPU?

Only a SQL Server or other services/apps running?

Which version of 2000 and what service packs?

"and when reports are run." What reports?
Avatar of perksdev
perksdev

ASKER

the application is timing out,   its auctually a webpage so whenever the page tries access the DB it retuns an error to the users.

this over a LAN

3GHz processor with 4GB Mrmory

This is only a sql server no other apps or services run on it

SQL Version is SQL 2000 Enterprise with SP4

I think we got the Reports figured out

Right now the only issue is when the Trasaction logs backup hourly it gives timeout errors  the logs are backed up to a local dirve.
Then I would start looking at disk activity.

Where are your bak/trn files being saved vs the location of your mdf/ldf files.

Are you using NAS or SAN?

Bring up perfmon and watch the disk reads/writes per sec and page faults. Throw in memory and CPU for grins.
No I am not using a SAN or NAS
disk read/writes per sec seem ok
I am noticing that the CPU is extremely high 70 to 100% almost constantly
ASKER CERTIFIED SOLUTION
Avatar of Jim P.
Jim P.
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I don't really get any errors other than the task mnager showing  sqlservr.exe between 80 and 100% cpu utilization.  I've looked in the Event log and SQL logs  but have not been able to find anything.
Thanks for all of your help.  Sorry for the delay in accepting a solution.  The problem ended up being increase load and the solution ended up being query optimization.  Thanks again!
Glad to be of assistance. May all your days get brighter and brighter.