THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is

Quick Database Connectivity Testing

This blog has moved! You can find this content at the following new location:

Published Friday, August 26, 2011 1:00 PM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Chuck Rummel said:

Another way I've used before on web servers is to set up a new ODBC connection.  You can use the Test Connection button and then delete the connection you just created.

August 27, 2011 11:12 PM

Christian Nitz said:

There are these other possibilities for the outcome of the test step:

1: Microsoft Data Link Error

"Test connection failed because of an error in initializing provider.[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied."

In my experience this is never actually access denied, and is always a connectivity problem. (firewall, port, ip, etc.)

2: Microsoft Data Link Error

"Test connection failed because of an error in ititializing provider. Login failed for user '<username>'."

In contrast to the other error message, this one does indicate access was denied while the connection itself was successful.

August 29, 2011 2:31 PM

Robert L Davis said:

Very handy! I have a VBS script that I use for this, but this is much simpler!

September 12, 2011 11:18 AM

kaka said:

Thanks a lot, you have helped me.

June 21, 2012 7:10 AM

Jane said:

Fantastic. Thank you.

September 14, 2012 6:28 AM

Leave a Comment


This Blog



My Latest Book:

Community Awards

Friend of Red Gate

Contact Me


Privacy Statement