February 6, 2014 at 10:23 am
I am trying to understand what these settings mean but BOL is not making it clear enough for me.
I want to change these 2 config parameters on server A.
Remote Login Timeout: the time it takes for a remote process to be able to successfully login to server A before timing out.
Remote Query Timeout: the time it takes for a remote query to execute on server A (using a linked server) before timing out.
Is my understanding correct?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 6, 2014 at 7:49 pm
Remote Login Timeout: the time it takes to authenticate on a linked server before timing out. For example, if you are trying to log in to a remote server and that server is down, remote login timeout helps make sure that you do not have to wait indefinitely before your computer stops trying to log in - 0 means wait indefinitely.
The other one is fine.
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
February 7, 2014 at 3:13 am
MyDoggieJessie (2/6/2014)
Remote Login Timeout: the time it takes to authenticate on a linked server before timing out. For example, if you are trying to log in to a remote server and that server is down, remote login timeout helps make sure that you do not have to wait indefinitely before your computer stops trying to log in - 0 means wait indefinitely.The other one is fine.
Hi,
Thank you for the reply.
I have a couple of follow-up questions:
(1) Does it only apply to linked servers? (What about .NET-SQLClient, ODBC or other types?)
(2) If we configure the setting to 0 on server A, then any login attempt to server A will be able to wait indefinitely; is this correct?
Thanks again,
Marios
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 7, 2014 at 5:55 am
1) Sort of, and 2) Yes.
If you are using a linked server via MSSQL then it applies, if you're setting up an a linked server via an ODBC or a system DSN then it still applies (but I believe you can also set the timeout property via the ODBC applet itself).
Yes, zero means it will wait indefinitely (or some other process times it out from the other side)
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply