August 30, 2010 at 5:07 pm
I manage a web application. This app calls a stored procedure. The stored procedure works most of the time but sometimes it hungs and produces the following error:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
This happens on an off. It works most of the time but as I said it also hungs up often.
The database is being shared by the web application and also a windows application. Both applications could be accesing the same tables simultaneously.
This error always occurs on the web application and never from the windows application.
Is there a way of avoiding this error. Any suggestions.
Thanks,
Rafael
August 31, 2010 at 5:33 am
Try running a SQL Profiler trace and watching what happens when you call the SP from your web application. Include the deadlock graph to see if you're experiencing deadlocks too
August 31, 2010 at 11:04 am
I have the sql 2005 workgroup edition. I don't think sql profiler comes with it. Is there a download available ?.
August 31, 2010 at 11:15 am
Profiler is included in every edition other than Express.
It won't be deadlocks, they give different errors (error 1205 if I recall). A timeout is a client-side error where the client app decides that the server is taking too long to process the operation. It's typically a result of poorly written queries and/or poor indexing.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply