April 27, 2020, 9:52pm
I'm using SSMS 2012.
Does anyone know why there is a default time out on SQL Servers of 600 seconds?
I've increased it to 1800 seconds, in case I take a break for lunch, for example.
But I was wondering whether therew would there be a problem with increasing it?
I'm thinking of setting it at 3600 second.
Is it not recommended to change it to a high number?
What is the requirement that needs to have that setting changed? Is something timing out?
April 27, 2020, 11:43pm
Yes, SSMS times out if you haven't been active for 600 seconds.
So if you needed to do some working in another application, you HAVE TO connect to the server again (manually), which is annoying.
April 28, 2020, 1:03pm
Wait. In 2012? Where are you setting this timeout?
April 28, 2020, 11:53pm
Using SQL Server Management Studio
In Object Explorer, right-click a server and select Properties.
Click the Connections node.
Under Remote server connections, in the Remote query
timeout box, type or select a value from 0 through 2,147,483,647 to set the maximum number seconds for SQL Server to wait before timing out .
April 29, 2020, 7:58pm
I think this isn't saying exactly that. This is for remote server connections from other SQL Servers.
Books Online says (I marked the relevant bit in italics):
Remote Server Connections
Allow remote connections to this server
Controls the execution of stored procedures from remote servers running instances of SQL Server. Selecting this check box has the same effect as setting the sp_configureremote access option to 1. Clearing it prevents execution of stored procedures from a remote server.
Remote query timeout (in seconds, 0 = no timeout)
Specifies how long (in seconds) a remote operation may take before SQL Server times out. The default is 600 seconds, or a 10-minute wait.
Require distributed transactions for server-to-server communication
Protects the actions of a server-to-server procedure through a Microsoft Distributed Transaction Coordinator (MS DTC) transaction. For more information, see Configure the remote proc trans Server Configuration Option.
I do think Azure boots you out if you've been connected too long. But I don't think it's that setting.