On the Connect to Server window, click Options. In an unconnected-to-anything state and from the empty Object Explorer window, click New Query from the toolbar. This is despite the fact that the registered server's Connection Properties show a default value for Execution time-out to be 0 seconds. There I see that Execution time-out is 600 seconds. In the new query window, right-click and click Query Options. Right-click the server from the Registered Servers list. Or is that you select the server from the dropdown in SSMS? There is an execution timeout under Options, so if you select it from the dropdown I guess it's taken from what's been saved there. So if I follow you clearly: you have now determined that the setting of 600 comes from a registered server, and you get the timeout if you open from Registred servers? Every time that I create a new query instance, the timeout is being set to 600 seconds.
I've deleted and added that registered server. I'll add that I can't get the setting to "stick". I opened a new single query and it was set to 0. IĬlicked on the Restore Defaults and it set to 0. However, I found that on a single query instance, it was set to 600 seconds. I have to be honest that I only looked at the "permanent" solution above. To change it on a permanent basis, go to Tools->Options->Query Execution. However, it is possible to configure an execution time, and apparently you (or your best friend who likes to pull your legs) have set it to 600 seconds.įor a single query window, right-click in the editor window and select Query Options and this will directly take you to the tab with the timeout. We can tell that it does not come from SQL Server, since the message number is negative.īy default, a query window in SSMS waits forever. The timeout period elapsed prior to completion of the operation or the server is not responding.