Real-time alerts · Agentless · Built in T-SQL
SQL Server monitoring that lives in SQL Server.
SQLBeat watches your SQL Servers, Windows servers and IIS sites from one dedicated instance and emails the right people the moment something goes wrong. Every metric, alert and change lands in a warehouse you can query, so when an incident hits, the evidence is already there.
Free to use, in any organization. Optional support retainer from the team that built it. See pricing
-- Alerts SQLBeat raised in the last hour select ymd, serverName, severity, subject from notificationLog where ymd > dateadd(hour, -1, getdate()) ymd serverName sev subject 09:41:07 SQLPROD02 1 Blocking: spid 87 blocked 6 sessions for 41s 09:38:55 SQLPROD01 2 Log file for Orders grew 38% in 1 hour 09:30:12 WEB04 2 Application pool OrdersApi stopped 09:12:40 SQLPROD03 3 Index ix_orderLines_sku not used in 30 days -- Every metric stays queryable for as long as you keep it select * from v_performanceLog_all where serverName = 'SQLPROD02'
What it monitors
Four modules, one place to look.
SQL monitoring is the core; the other modules build on it. All of them run on the same SQLBeat server and write to the same warehouse.
SQL Server
Blocking, runaway queries, job failures, backups, integrity, file growth and capacity, waits, indexes, replication and log shipping.
SQL monitoring →Windows
Event logs, any WMI counter, services, CPU and disk queues, processes, ping and IP changes, syslog from network devices.
Windows monitoring →IIS and weblogs
Reads IIS and Apache logs in near real time into a normalized warehouse, plus application pool health and configuration drift across a web farm.
Web monitoring →Audit and change
A history of every procedure, table, index, login and permission change, with before-and-after text, plus config files and Active Directory.
Audit and change →Why it's different
No black box. It's all T-SQL.
Most monitoring tools hide their logic behind an agent and a proprietary store. SQLBeat is SQL Server code: every check is a stored procedure, every schedule a SQL Agent job, every alert a row in a table.
That means a DBA can read exactly what a check does, change a threshold, add a check of their own, or point Power BI or Grafana at the warehouse. No export step, no API.
- AgentlessMonitored servers need only the access SQLBeat's queries, WMI calls and file reads require. Nothing is installed on them.
- Rules-based alertsOne engine routes every alert by server, group, severity, text pattern and time of day, to any number of people.
- Open warehouseRaw detail in monthly databases, rolled up into day and week tables, kept three months by default or as long as you like. Query it in SSMS.
- Self-maintainingSQLBeat partitions, archives and trims its own data, and monitors itself.
- Any edition, old or newMonitors SQL Server 2000 through 2022, Express to Enterprise.
Free, with help when you want it
Free to use. A retainer if you want us on hand.
Free, for everyone
Businesses, public bodies and individuals use SQLBeat at no cost, on any number of servers, and can change it however they need.
Support retainer
A monthly retainer for direct help from the TTS team: installs, upgrades, troubleshooting and alert tuning.
Support pricing →Installation
Rather not set it up yourself? We'll install SQLBeat remotely for a fixed price and hand you a working system.
Installation →In production
Built for environments with no room for surprises.
SQLBeat was the monitoring and audit backbone for an automotive eCommerce platform running 30+ federated SQL Servers across four datacenters, and the evidence source for its annual PCI audits.
Questions? Ask in GitHub Discussions, where the people who use SQLBeat and the people who wrote it answer.
Community and support