Server tools

Right-click a server, open Tools, and act on the whole instance.

Right-click a server in the Object Explorer to act on the whole instance. These seven surfaces answer questions that are not about one database. The first five are in the server's Tools submenu; Server Variables is the Configuration and Status pages of the server's Properties..., and Open in Terminal is its own item on the server menu (and in the command palette).

ToolAnswers
Server Dashboard“Is this instance healthy right now?” - sessions, throughput, health, and resources as live tiles on a ticker.
SQL Agent“Did the overnight jobs run?” - jobs, history, schedules, operators, and alerts from msdb, with script-first job control.
Security“Who can get in, and as what?” - server logins, role membership, and the permissions each principal holds.
Connection Health“Which of my saved connections actually work?” - a badge, ages, last error, and a measured test latency per connection.
Disk Usage“What is eating the disk?” - every database on the instance sized, plus the current database's file layout.
Server Variables“What is this server counting, and how is it configured?” - searchable status counters and settings, with dynamic settings changed through reviewed SQL.
Open in Terminal“I just want the real CLI.” - the engine's own client in a terminal window, connection filled in, password passed by environment.

Reading is live; changing is scripted

The dashboards and grids read the engine's own views and refresh as you watch. Anything that alters the instance (enabling or starting a job, changing a login) is written into a query tab as SQL for you to review and run. That keeps the change in your history and out of a dialog's private business. Server Variables runs a changed setting from the Properties dialog instead, and only after a review sheet shows you the exact statements.

Connection Health is the odd one out. It is not about the server you right-clicked at all: it surveys every saved connection. It lives here because that is where you look when something is wrong and you do not yet know which target is at fault.

Engine coverage: Server Dashboard and Disk Usage work on every engine with a native driver - SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, libSQL/Turso, DuckDB, ClickHouse, Oracle, and Redis; the Security editor covers SQL Server, PostgreSQL and MySQL/MariaDB, with a read-only view on ClickHouse; SQL Agent is SQL Server's own. See the per-engine matrix.

Permissions are the server's, not the app's. A tool shows what your login can see, an instance-wide view generally needs an instance-wide permission, and where you lack one, SQLly reports the server's own refusal rather than an empty grid.

In this section

Server Dashboard
Live health tiles for a connection - sessions, throughput, health, and resources - refreshed on a ticker.
SQL Agent
Browse jobs, history, schedules, operators, and alerts from msdb, with script-first job control.
Security
Server logins, role membership, and permissions in one place.
Connection Health
Every saved connection's observed health - badge, ages, last error, and a measured test latency.
Disk Usage
Size every database on the instance, plus the current database's file layout.
Server Variables
Search status counters and configuration, and change dynamic settings through reviewed SQL.
Open in Terminal
Drop into psql, mysql, sqlcmd, redis-cli and friends with the connection already filled in.