Sometimes, it can be useful to validate SQL connection settings outside GSX Monitor. This will help validating Database connection string and user credentials when troubleshooting issues for example.
This article describes how to create .UDL files to validate SQL Client connectivity from Windows.
How it Works
GSX Monitor relies on SQL queries to determine service availability and collect statistics for the following monitored platforms:
- Microsoft SharePoint
- BlackBerry Enterprise Server
- IBM Notes Traveler
To validate SQL client connectivity, you need to know SQL connection details:
- SQL Server name: usually FQDN (like: servername.domain.name)
- SQL Server Instance Name: default is "MSSQLSERVER"
- SQL Server network port: default is 1433
- SQL Server security: Windows or SQL authentication
- SQL Database name
- SQL Database credentials
A sample SQL Test connection.udl file is attached to this article.
Here are the steps to reproduce SQL client connectivity used in GSX products. This procedure will allow you to validate all the SQL connection information that will be required to configure SQL checks in GSX Monitor.
- Create a new .txt file named "Test SQL Connection.txt".
- Rename the file extension from ".txt" to ".udl" (be sure to display file extensions; by default extensions are hidden and the real file name will end up being "Test SQL Connection.udl.txt")
- Double-click the Test SQL Connection.udl file:
- Enter the related information, reproducing what is set up in GSX Monitor (platform dependent):
- This example uses default SQL settings with SQL authentication:
- This example uses default SQL settings with explicit Windows Authentication:
- This example uses explicit SQL settings with integrated Windows authentication:
- Successful connection:
- Bad credentials:
- Bad SQL Server/Database setting: