Microsoft SQL Server
See who is blocking whom, what the server waits on, and whether backups, jobs and availability groups are healthy, with a read-only monitoring login.
What it answers
Questions an on-call engineer asks, which an AI client can answer with this plugin.
- Which session is at the head of the blocking chain, and what is it holding open?
- What has the server spent its time waiting on - locks, disk, memory or the log?
- Who is connected, and which sessions sit idle with a transaction open?
- Which databases have no recent full backup, or no log backups?
- Is the availability group healthy, and how far behind is each secondary?
- Which data or log file is full, cannot grow, or has slow I/O?
- Which Agent jobs failed, at which step and with which error?
- What is using tempdb, and which session uses the most?
- Which transaction has been open the longest, holding up the log?
What it returns
Each of the plugin's read-only tools, described in words.
- SQL Server requests blocked by another session, each with what it waits on, the session blocking it, whether that blocker is the head of the chain and how old its transaction is
- What SQL Server has spent its time waiting on since it started, from sys.dm_os_wait_stats with idle and background waits left out, largest first
- User sessions on SQL Server with their login, client, database, state, current wait, blocker, open transactions, CPU, reads and the statement, normalised
- Each SQL Server database with its recovery model and the time of its last full, differential and log backup from the msdb history, never backed up first
- Always On availability groups on this SQL Server - each replica's role, connection and health, and each database's synchronisation state, send and redo queues
- Every SQL Server data and log file with its size, growth setting and limit, I/O counts and stall times since start, and the free space on its volume, largest first
- SQL Server Agent jobs that failed or were cancelled in the last hours, newest first, with the step that failed and its error number and severity
- SQL Server tempdb space in one row - size, free, user objects, internal objects, version store and mixed extents, and the session using the most of it
- Open SQL Server transactions oldest first, with the session, login and database, age, kind, log space used and the session's last statement, normalised
At a glance
- Plugin
- sqlserver 1.0.0
- Publisher
- levantar
- Platforms
- Linux, Windows
Tested on
- SQL Server 2019, 2022 and 2025 Developer on Linux (Ubuntu, Docker), CI runner
- SQL Server 2022 Express on Windows Server, CI runner
How it logs in
Without an explicit choice, install tries the methods that need no secret first, in this order.
- A user name and password
- Windows integrated sign-in, as the agent's account, with no secret
The least-privilege login
The grant script in the pack. secronyx plugin setup sqlserver --apply runs it with a random password for the new login, or you can run it by hand.
See it run
Recording coming. Install, setup and status runs for this plugin are recorded on the shared test lab, and appear here once they have run.
Read-only, in layers
Every query is fixed text inside the signed pack: one SELECT or WITH statement whose functions are all on the agent's allowlist for that database. It runs in a READ UNCOMMITTED transaction with server-side statement and lock timeouts, and is always rolled back. Callers can only fill in typed, bounded arguments, which are bound as parameters.
These controls narrow what the plugin can do; none of them is a guarantee on its own. An administrator can still accept a more powerful login on purpose (audited and shown in status), root or Administrator on the host can replace the agent, and the plugin can read whatever its login can see.