3305 Main Street Ste 019 Vancouver, WA 98663

How do I test my connection to my SQL Server database?


You can perform a basic connectivity test using software that is already installed on your workstation. This may be helpful when troubleshooting issues with Event 1 Integrator or when using Liberty Reports for SQL Server.

  1. Start ODBC Administrator (32-bit). With Windows XP, you will find this in Control Panel within Administrative Options. For all other operating systems, look for the ODBC program group on the Start/Programs menu.
  2. Click the User DSN tab
  3. Click Add
  4. Scroll down and select SQL Server
  5. Click Finish
  6. In the Name box, type: TestDSN
  7. In the Server box, click the drop-down and select the name of your SQL Server. If your server does not appear in the list, you can type it.
  8. Click Next
  9. Specify login properties.
    For diagnosing Integrator issues, select the second option (With SQL Server authentication using a login ID and password entered by the user). Then enter the user name and password that you are using within Integrator.
  10. Click Next. If a connection cannot be made to the server, you may receive an error notice at this point.
  11. Check the box entitled: Change the default database to
  12. Click the drop-down button and select the name of the database you are trying to connect to
  13. Click Next and then Finish
  14. In the next window that comes up, click Test Data Source. If the connection is successful, the test results will indicate TESTS COMPLETED SUCCESSFULLY, otherwise an error message will be displayed.

If you are unable to complete a successful test connection to your database by following the above process, your connectivity issue is caused by something outside of the Event 1 Software product you are using. You should consult with a qualified IT professional or database administrator in order to resolve the connectivity issue. Possible causes of a connectivity issue include:

  • Incorrect name for the server or instance
  • Incorrect user name or password
  • Insufficient permissions within SQL Server to access the given database
  • Problem with the name resolution for the server name
  • Firewall or other network related routing issues
  • Server load or network traffic