What would be a very fast way to determine if your connectionstring lets you connect to a database?
Normally a connection attempt keeps the user waiting a long time before notifying the attempt was futile anyway.
-
What about connecting to the target machine and port over tcp/ip and seeing if theres something listening there. I often telnet to a port just to see if something accepts the connection.Sam– Sam2015-07-07 04:54:58 +00:00Commented Jul 7, 2015 at 4:54
-
that might work, but creates other code than the standard database connection library, plus it doesn't guarantee the database will accept your connectionJorrit Reedijk– Jorrit Reedijk2015-07-07 08:33:58 +00:00Commented Jul 7, 2015 at 8:33
Add a comment
|
2 Answers
You haven't mentioned what database you are connecting to, however. In SQL Server 2005, from .NET, you can specify a connection timeout in your connection string like so:
server=<server>;database=<database>;uid=<user>;password=<password>;Connect Timeout=3
This will try to connect to the server and if it doesn't do so in three seconds, it will throw a timeout error.
Comments
Shorten the timeout on the connection string and execute something trivial.
The wait should be about the same as the timeout.
You would still need a second or two though.
