SQLlyServer Dashboard
✓ functionalLive health tiles for a connection - sessions, throughput, health, and resources - refreshed on a ticker.
The Server Dashboard is a live, read-only health view for a single connection. It reads catalog and dynamic-management snapshots on a five-second ticker and lays them out as metric tiles, so the state of the instance is legible at a glance rather than buried in a dozen queries you have to remember. Each tile shows the metric, its current value, and a sparkline of the last five minutes so a trend is obvious before it becomes a problem.
Sessions
Connections (against the configured maximum), running requests, blocked count, idle-in-transaction, longest query, and oldest open transaction.
Throughput
Transactions, queries, rows read, and slow queries per second - computed from the engine's cumulative counters between refreshes.
Health
Deadlocks and lock waits per second, temp spills, and replication lag - the numbers that tell you something is fighting.
Resources
Cache hit ratio, page life expectancy, memory in use, storage and reclaimable space, object counts, and uptime.
It is non-modal and there is one dashboard per connection, so you can open several and watch multiple servers side by side; each new pane cascades slightly so none hides another. Refresh and pause act only on their own pane, and a status line shows how fresh the numbers are. Footer buttons jump straight to Activity Monitor, Query Insights, and Disk Usage for the same connection, and a per-database sizes grid fills the bottom of the pane.
VIEW SERVER STATE grant - only its tiles disappear, and the pane names what was unavailable instead of pretending the number is zero.
Tiles adapt to the engine - PostgreSQL adds idle-in-transaction, shared buffers, and replication lag; MySQL and MariaDB add slow queries (read from their respective status tables); SQLite, being a file rather than a service, shows only the Resources band: storage, reclaimable space, and object counts.