Aug 24, 2011
We have developed a VB 2008 app that uses SQL Server 2005 Express to store data collected by this app. This app has been designed to allow multiple connections to the one centralized database.
View 2 Replies
I have ran a few tests, and confirmed that if one computer running our app is accessing a database residing on a different computer,and the network connection between two computers has been severed, it would take approximately 3.5 minutes before I would get a connection timed out exception error from within my code.
I have deliberately set the ConnectTimeout property in the SQL connection string to be 15 seconds. But some how, SQL database engine still retries until approx. 3.5 minutes later.
My thinking is that I have a subroutine that would attempt to open a database once a minute.If the open attempt is not successful, and resulted in an exception, then I would popup a message to notify the user that the connection is not available.
Doing it this way, I have confirmed that it would take about 1.5 minutes for it to re-establish the connection, once the actual network connection has been restored.
To make the long story short, I would like to find a way to shorten the detection for a broken connection, and let the user know sooner, rather than locking up the app during the 3.5 minutes period has elapsed, and at the mercy of the SQL database engine to timeout. And why would it take 3.5 minutes to timeout the connection attempt when I had explicitly use 15 seconds in my connection string?