Server tools

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

Right-click a server in the Object Explorer, open Tools, and act on the whole instance. These are the five surfaces whose questions are not about one database.

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.

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.

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.

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.