Are you using Microsoft SQL Server? Use IDERA Uptime Cloud Monitor to monitor your Microsoft SQL Server performance.
Uptime Cloud Monitor from IDERA (UCM) offers a SAAS based out-of-the-box solution for monitoring Microsoft SQL Server for performance and availability. If you are not familiar with the concept of custom metrics as used in Uptime Cloud Monitor, please go through Custom Metrics information once before continuing with this document.
There are three steps that you need to do to start monitoring a Microsoft SQL Server:
Figure 1: In your Uptime Cloud Monitor Account, navigate to Databases>Getting Started
Login to your Uptime Cloud Monitor account and navigate to Custom tab -> Getting Started. Click on Microsoft SQL Server icon. .
Figure 2: The Microsoft SQL Server agent installation script
Click on icon to copy the installer script to your clipboard. Paste the command into the terminal window on the server where you want to install the agent. Script can be run on the server running Microsoft SQL Server, or it can be a different server, but this server will need to be continually running in order to monitor Microsoft SQL Server.
As soon as the script is run on a terminal with root access, it starts downloading the required Microsoft SQL Server monitoring agent on your server. You will need to configure the following items in the agent installation process. Item specified in square brackets ( [ ] ) are the default.
Figure 3: Executing the Microsoft SQL Server agent installation script
Figure 4: Executing the Microsoft SQL Server agent installation script with monitoring frequency as 60 seconds
2. Monitoring frequency: 15, , 300, 900, 3600 seconds
Figure 5: Executing the Microsoft SQL Server agent installation script with group name as “MSSQL”, group label as “SQL Server Metrics” and Dashboard as “SQL Server”
3. Group label, group name and dashboard name for custom metrics [MSSQL][SQL Server Metrics][SQL Server]
Figure 6: Executing the Microsoft SQL Server agent installation script with unique name, authentication type, server hostname , username, password. Only one Microsoft SQL Server is added for monitoring.
4. Unique name for this server (good to differentiate if you are monitoring different Microsoft SQL Servers). [instance1 is default] 5. Server Name 6. Authentication type, hostname username,password(for sql authentication). We are choosing Windows Authentication mode in this illustration. 7. After configuring one database, you’ll get an option to add more Microsoft SQL Servers.
Figure 7: Executing the Microsoft SQL Server agent installation script with an upstart init file and the default value for log file name. The installation completes successfully!
8. Configure Microsoft Azure SQL Server[Default : N]
Navigate to Dashboard and you will see a new Microsoft SQL Server Dashboard has been added automatically by the installer.
Figure 8: A new Dashboard for Microsoft SQL Server has been added
As the installed script executes, you will notice data samples appearing on the widgets for this Dashboard.
Figure 9: Widget inside Microsoft SQL Server Dashboard displaying cache hits ratio.
Figure 10: Widget inside Microsoft SQL Server Dashboard displaying batch requests per second.
Figure 11: Widget inside Microsoft SQL Server Dashboard displaying checkpoint pages per second.
Uptime Cloud Monitor currently monitors 29 metrics which cover most of the important metrics for Microsoft SQL Server from a performance and stability perspective. You can see these 29 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [SQL Server Metrics] that was given as installation input. For some of these metrics, alerts have been automatically created (see section 3 below). To create new alerts see section: Configuring your own Alerts for the Microsoft SQL Server Database.
The metrics are:
As soon as your Microsoft SQL Server Database Monitoring Dashboard comes up, you will notice that some alert configurations have been automatically created by our Installation Script (under Alerts > Configure Alerts). These pre-configured alerts for Microsoft SQL Server Database include:
Active Parallel threads
Current number of active Parallel threads
Current number of active requests
Current number of active transactions
Average CPU utilization
Number of deadlocks
Count of deadlocks
Alert when Number of Deadlocks greater than or equal to 1.
Open connection count
Count of open connections
Count of blocked processes
Alert when processes blocked greater than or equal to 1.
If the alerting condition is met for these pre-configured alerts, some alert notifications may also be triggered.
Figure 12: A new alert being added that will be triggered when cpu usage metric exceeds a threshold of <entered value> within a time period of 1 min
Alerts can also be configured against any of these 29 monitored metrics for Microsoft SQL Server.
You can configure new alerts that will be triggered when performance issues with Microsoft SQL Server arise. You can also configure the notification mechanisms for a triggered alert.
Uptime Cloud Monitor supports notifying different sets of users with differing notification mechanisms for each alert type.
Notification mechanisms include:
Webhooks are also exposed for clients to configure custom notification mechanisms. More about setting up website probe alerts can be found here.
Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no Credit Card required).
You can find more information about Uptime Cloud Monitor pricing options here.
We charge only $0.08 per month per metric!
Sign up today!