Connection Timeout
-
How to increase time of SQL connection timeout property in VB.NET
You should use the SqlConnection.ConnectionTimeout property to adjust the timeout time of the connection. Here[^] is the MSDN page which gives some examples. Hope this helps
When I was a coder, we worked on algorithms. Today, we memorize APIs for countless libraries — those libraries have the algorithms - Eric Allman
-
How to increase time of SQL connection timeout property in VB.NET
-
Why would the network have anything to do with the connection timeout requirements? If he is running a long stored proc then the timeout is relevant on the connection and the network latency is irrelevant.
Never underestimate the power of human stupidity RAH
-
Why would the network have anything to do with the connection timeout requirements? If he is running a long stored proc then the timeout is relevant on the connection and the network latency is irrelevant.
Never underestimate the power of human stupidity RAH
-
Is that not CommandTimeout?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I beleive there is a difference but would have to look it up, probably the command timeout is effective for the current command where a connection timeout is for all commands on the connection.
Never underestimate the power of human stupidity RAH
-
I beleive there is a difference but would have to look it up, probably the command timeout is effective for the current command where a connection timeout is for all commands on the connection.
Never underestimate the power of human stupidity RAH
On the app I wrote for working with large datasets that can take over an hour to process certain fetch events, I have set my connection timeout to 5 seconds, and the command timeout to 0 (ie never timeout). works a treat.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
On the app I wrote for working with large datasets that can take over an hour to process certain fetch events, I have set my connection timeout to 5 seconds, and the command timeout to 0 (ie never timeout). works a treat.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Sure but that has nothing to do with the network :-D
Never underestimate the power of human stupidity RAH
-
Sure but that has nothing to do with the network :-D
Never underestimate the power of human stupidity RAH
Thats why you confused me with this;
Mycroft Holmes wrote:
If he is running a long stored proc then the timeout is relevant on the connection
The long running should be on the command, not the connection, or you should have said irrelevant on the connection. Anyway, doesn't matter, we'll leave it there, I need a cuppa...... :)
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
Why would the network have anything to do with the connection timeout requirements? If he is running a long stored proc then the timeout is relevant on the connection and the network latency is irrelevant.
Never underestimate the power of human stupidity RAH
-
Mycroft Holmes wrote:
Why would the network have anything to do with the connection timeout requirements?
What other enterprise constraint would require changing it?
You seem to have taken a severe left turn, the OP was asking about how to change the connection timeout and you are now pursuing enterprise level network information. The guy may be working on a single user, personal application he is learning on (considering it is VB this is even more likely) and needs to cope with a long running stored procedure.
Never underestimate the power of human stupidity RAH
-
You seem to have taken a severe left turn, the OP was asking about how to change the connection timeout and you are now pursuing enterprise level network information. The guy may be working on a single user, personal application he is learning on (considering it is VB this is even more likely) and needs to cope with a long running stored procedure.
Never underestimate the power of human stupidity RAH