timeout period elapsed prior to completion.

Question

timeout period elapsed prior to completion.

SQL Galaxy

One Orange Chip

Points: 29472
More actions
July 3, 2014 at 1:07 am

#287562

Application Error during upload data into database,.
The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated.
Dev team asking to DBA it was issues on database and server side and resolve it.
I checked at DB level blocking and running process, it seems wokring well, Further where to be troubleshoot for resolve timeout problem?
have tried everything... checkin the locks.... blocking..
Thanks
ananda

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Grant Fritchey SSC Guru Points: 398909 More actions · Answer 1

If a process has timed out, you won't see blocking now. There may have been blocking during the process. Depending on how long things were running, I'd suggest taking a look at the system_health extended event session. You can see many long running queries and long held blocks stored there. It can help you understand what was happening.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Sean Lange SSC Guru Points: 286590 More actions · Answer 2

It might not show up in long running queries either. This is a result of a query that ran longer than the timeout that was established in the connection. The default is 30 seconds but it can be set a lot shorter. I would start with the query or stored procedures that are executed from the application. Hopefully the dev team has logged this error so you have at least a general idea of where in the code this happened. Then evaluate those queries and see if there is something that needs some tuning. Also, check with the dev team about what the connection timeout is set at. If it is set to 10 seconds and this runs 11 seconds it will timeout.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 3

Yes, resolved that issues and CPU resource reduced upto 80%..

I am not changed default connection at instance side.

1. capture the query duration time at SQL profiler which are the query taking > 5 seconds (5000)

2. Executed those queries at SSMS with actual exec.plan and found the missing index details.

also helped me lot Mr.Jonathan Kehayias - Digging into the SQL Plan Cache: Finding Missing Indexes

Thanks

ananda