Home Dashboard Directory Help
Search

The timeout for Query Execution is difficult to set for local connections by Erland Sommarskog


Status: 

Closed
 as Won't Fix Help for as Won't Fix


10
0
Sign in
to vote
Type: Bug
ID: 286298
Opened: 7/6/2007 1:54:41 AM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description

Running against the local server, I open Options->Query Execution->SQL Server->General and change the timeout to, say, 1. I open a new query window and run "WAITFOR DELAY '00:00:20'". Despite the timeout the query runs to completion. I restart SSMS and try again, the same result. But if I now open a window to a remote server, and run the command, I get a timeout error quickly. And if I know switch the connection to the local server, I still get the timeout. In fact, if I now close SSMS, open it again, and run against the local server, I get the expected timeout error. Amazing! :-)


Details
Sign in to post a comment.
Posted by mrdenny on 9/11/2009 at 1:28 AM
Eric, This has been open for quite a while. Any status update that you can provide?
Posted by Microsoft on 7/9/2008 at 11:42 AM
Hi Erland,
This is in fact a real bug. You have three choices for working around the problem:
1) When you make a new connection you can configure the execution time-out on the connection dialog.
2) On an existing query window you can right-click, select "Query Options" and set the execution time-out for this particular query window.
3) When registering a server you can set the execution time-out. When you connect a new query window from registered servers it'll use the execution time-out set on the server registration.

Here's the badnews, we broke the last one in SQL2K8. I just discovered it while testing this bug. We won't be able to fix it for RTM.

Cheers,
Dan
Posted by Microsoft on 10/5/2007 at 9:28 AM
Thank you for reporting this issue. It is repro'ed in the current version and we will investigate, address the fix in a future release.

Regards,
-Eric
Posted by Microsoft on 10/5/2007 at 9:26 AM
Thank you for reporting the issue. It is repro'ed in the current version. We will investigate and address the fix in a future release of SQL Server.

Thanks,
-Eric Kang
Sign in to post a workaround.