Default Timeout Period in SQL Server

Question

I got the error

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

during the command execution.

I also set Connect Timeout=60 in the connection string.

That stored procedure execution time is around 35 seconds.

Connection is established, but result is not returned.

https://stackoverflow.com/questions/847264/what-is-the-difference-between-sqlcommand-commandtimeout-and-sqlconnection-conne — Sarvesh Mishra, Feb 08 '19 at 06:16
Possible duplicate of [What is the difference between SqlCommand.CommandTimeout and SqlConnection.ConnectionTimeout?](https://stackoverflow.com/questions/847264/what-is-the-difference-between-sqlcommand-commandtimeout-and-sqlconnection-conne) — Stefan Becker, Feb 08 '19 at 06:24
Have you thought whether it is possible to optimise your stored procedure? — Steve Ford, Feb 08 '19 at 09:20

score 7 · Accepted Answer · answered Feb 08 '19 at 06:16

7

DbCommand has CommandTimeout, which is what you want here - it is set per command; the "connect timeout" only impacts, reasonably enough, what the timeout is for connecting. The default value for CommandTimeout on SqlCommand is 30 seconds.

answered Feb 08 '19 at 06:16

Marc Gravell

1,026,079
266
2,566
2,900

score 0 · Answer 2 · answered Feb 08 '19 at 08:05

0

You can also extend connection timeout in connectionstring

;Connection Timeout=30

See: Connection timeout for SQL server

answered Feb 08 '19 at 08:05

VoonArt

884
1
7
21

that is the timeout for *connecting*, not for *executing*. You cannot set the execution timeout in the connectionstring – Hans Keﬆing May 03 '23 at 10:16

Default Timeout Period in SQL Server

2 Answers2