April 24, 2006 at 3:12 pm
Got timeout expired issue. Checked the error log and event log, couldn't find any error. There was already a trace running at that time, which showed that one stored proc is taking more than 30 secs.
Could this be a network issue as this request is comming from Australia to US server? Hoping this is not a network issue.
April 24, 2006 at 3:31 pm
A timeout expired error could be a number of things, network included. The error means just what it says, there is a timeout occuring either in the database, session, or application code. This timeout could be due to a database request waiting on server resources (if your server is either CPU, Memory, or Disk bound) or network resources. It is also a sign that you need to do some t-sql query or index tuning.
You said that you had a trace running? How did you memory, disk, and cpu look at the time of the error?
April 24, 2006 at 8:31 pm
My trace doesn't have those things included. There are other tools through which I can know memory, disk and CPU utilization, which are looking fine.
Network Summary - Total_MB/Sec
Network Packet Rates - Packets_in_per_sec
- Packets_out_per_sec
NetworkErrors - Packet_errors
Does any of the above three can help in finding the network I/O?
April 25, 2006 at 8:11 am
It looks like those counters have more to do with activity. Watching them could over a period of time could tell you how active your network card is. You may also want to include Network Interface>>Output Queue Length. This would tell you if there are network delays (either in your network card, or somewhere on your network) that are forcing packets to wait. If you think it may be a network related issue, I would get your network guys involved as soon as possible.
April 25, 2006 at 9:07 am
If the server trace shows that the procedure was running more the 30 sec it has nothing to do with network. I too would monitor the available memory but meanwhile I would get code that this stored procedure is running, run it in Query Analyzer with showing the execution plan and see where did the time go.
Regards,Yelena Varsha
April 25, 2006 at 10:11 am
I guess I got away from what he'd originally stated about the stored procedure running for more than 30 seconds. Yelena is correct, look at the stored procedure code. If your memory, cpu, and disk are OK, you will need to either tune your sql code or look at your indexes.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply