Every SQL Server DBA would have faced situations similar to SQL Server not accepting connections for few minutes, SQL Server not responding for few minute or Applications not able to connect with SQL Server for few minutes. Before DBA’s gets alerted about the situation and starts troubleshooting the issue. Everything becomes normal. Challenge in this situations is it becomes very difficult to understand where the underlying problem was, It could be a network connectivity, Application server problem or It might be an issue with SQL Server itself. How do we collect diagnostic data to prove that SQL Server was stable at the time of issue (or) If the issue is with SQL Server then how to collect data we need for diagnosing the issue when there is issue?
SQL Monitor to monitor SQL Server Services
SQL Monitor monitors the SQL Server services and creates log if SQL Server service is down (or) If SQL Server is not accepting (or) SQL Server is not responding to Queries
How it works?
SQL Monitor checks the SQL Server in 3-Phases
1. Check the status of SQL Server service through the windows service control manager
2. If the service is running then check if SQL Server is accepting connections
3. If SQL Server is accepting Connections then probe to perform a simple query and see if SQL Server is responding properly.
4. If SQL Server is not accepting Connections then connect to SQL Server using DAC and take a stack dump.
How to Configure
1. Create a folder call SQLMonitor in C:\
2. Create a Text file called serverlist.txt to fill all the SQLServer information in your account.
Servername [TAB] Servicename;
3. Invoke command prompt and open attached SQLmonitor.EXE.
1. Multi-threaded . Each server and service is verified using its own thread so retrieving information from one server will not affect the pooling interval to other server.
2. Single exe can be scaled to monitor more than 1000 servers and 1000 services.
3. Uses few MB of memory and system resources.