SQL Server Monitoring

SQLBeat’s Database Monitoring framework is focused on automating the regular checks and maintenance that keep high-transaction multi-server environments running smoothly. By automating these checks, SQLBeat frees you up to take on the high value challenges – why spend your valuable time dealing with the routine?

User activity record

SQLBeat takes a snapshot of all user activity at an interval you define. This snapshot includes buffer contents, locks held, connection details and “wait” resource information. This complete and comprehensive activity history is available for query through the UI, or by accessing the table directly.

Database backups

SQLBeat watches your servers and alerts when key databases have not been backed up – a record of backups is maintained and available for query through the UI.

Data and Log files: Capacity planning

Never be surprised by out of control log files – let SQLBeat alert you if log files grow beyond a reasonable size. Disk free space and the size of data and log files are recorded and archived; this data is used to generate real-time capacity plans that alert based on historical growth patterns and a configurable “time to zero” mark. Further, SQLBeat will let you know if there are any abrupt changes in database sizes – to give you advance notice of any changes in usage patterns.

Monitor Jobs

SQLBeat continuously monitors your SQL jobs, and alerts you by email – with full detail – whenever it observes a failure. Use the message rules engine to define severities and tune which alerts you receive based on time of day!


When Replication or Log Shipping is detected on a monitored server, alert emails are generated whenever errors are detected – this applies to Transactional and Merge replication Distribution and Merge/Conflict errors.

Disaster Recovery Synchronization

SQLBeat can be configured to watch key tables, and to report when a Source and Target become out-of-synch, providing you a guarantee your DR servers are up to date.

SQL Error Log

SQLBeat watches the SQL Error log and is configured to automatically generate alerts in real-time when critical issues are detected.

Server Connectivity

SQLBeat monitors connectivity to each monitored server, including PING response time. Using this data SQLBeat can provide an accurate uptime report, as well as alerts when PING times to your servers change.

Blocking and “Runaway” Processes

Whenever a process is observed to be blocking, an email alert is generated that includes details on both Blocker and Blockee. Any process which consumes Disk or CPU resources past defined thresholds also generates an email alert, so that you can react quickly to conditions that may result in an impact to performance.

SQL Statistics

SQL Server’s full set of internal performance registers is recorded by SQLBeat and archived for query – this includes statistics from Page Life Expectancy to time-specific transaction rates for each database. This information is particularly valuable in post-event research, to track SQL resource consumption and identify points of weakness.

Services Running

SQLBeat will watch SQL’s services and alert you if they go on/offline.

Database integrity and fragmentation

Regular database integrity and fragmentation checks can be scheduled through SQLBeat’s UI; if errors are encountered, SQLBeat dispatches an email alert.

Page Life Expectancy

Among several key statistics, SQLBeat monitors Page Life Expectancy and generates email alerts whenever it drops below thresholds you define.

CPU and Disk queues

SQLBeat watches CPU and Disk utilization and maintains a record of any interruption to processing caused by queuing in either. Any observed queue in excess of thresholds you define generates an email alert.


Waiting – on disk, cpu, network or a remote OLEDB resource – can have a huge impact on perceived performance; let SQLBeat alert you when these issues begin, rather than your users!

Based on system activity and SQL Server 2000/2005/2008 specific performance counters, SQLBeat is able to accurately monitor - and, importantly, substantiate - SQL Server uptime. The SQLBeat Framework continually monitors SQL performance and this continuous record is stored in a local datamart for post-incident research, growth planning and auditing.