Introduction

To get started select the live alerts Icon and choose Live Report:

This report is intended to monitor if there are any issues in your environment. By default, no alerts are enabled. To add standard or custom alerts, simply click on the Edit Live Alerts button in the context menu.

Standard Live Alerts

• Failed Live Jobs - SQL Server Jobs failing will get flagged by this alert allowing you to take action to fix them.
• Database Not Online - flags databases with the status offline or single user.
• Agent Offline - reports on SQL Server Agent. The alert will not report if you are running on express.
• Low Space SQL Drive - will be reported when drives have less than 10% space. Volumes used only by tempdb (no other databases on the same drive) are excluded, because tempdb has exclusive access to those drives.
• No Comms - flagged when there is no connection to the server. Possibilities include the server being off, firewall blocking the connection or the server being to busy to accept connections.
• Incorrect UTC Time - if the time is more than 10 minutes out it will be flagged by the alert.
• Created Databases and Dropped Databases - Reports on newly created and dropped databases within the last 24 hours.
• Replication Issues - reports on SQL Server Replication typical issues allowing it to be easily monitored.
• Long Running Queries - flags queries that take more than 2 minutes to run.
• Lead Blockers - reports blocking chains where a session has been waiting for at least 10 seconds. See details below.
• No Server Activity Auditing in 24 hours - flags servers that have had nothing changed or reported within the last 24 hours as it would be unusual in production environments.

Alert Details

If the alert is red then SQLPro has detected an issue. You can click on the show more icon (top right of the alert card) to see more details.

Lead Blockers details

The Lead Blockers detail grid shows a blocking hierarchy:

• * LEAD BLOCKER * - a session that is blocking others and is not itself blocked
• Blocked Session - a session waiting on another SPID

Useful columns include BlockingRole, Spid, BlockedBy, NumberOfBlockedSpids, WaitTime, WaitType, LoginName, HostName, DatabaseName, and a short SQLText preview. Rows are ordered so lead blockers appear first, then by how many sessions they block and wait time.

Alert History

The alerts also have history for any past alerts that were fired. To view the alert history click on the show history icon (also top right of the alert card).

Here you can change the time period for the history by changing the From or To date. By default, the history is one week in the past until now.

Secondly, you can view the details of the past alerts by clicking on one of the nodes in the graph. If you hover over one of the nodes it will show you date and the count of the errors for that time.

In the example below we are hovering over the node from 2022-09-30 14:56 and there were 5 issues.

If we click on the node we can see the 5 issues in the details section.