SQL Agent Jobs Manager
Visually browse, create, edit and control SQL Server Agent jobs
directly from VS Code — an SSMS Object Explorer / Job Properties
alternative that never leaves the editor.
Getting started
- Click the SQL Agent Jobs icon in the Activity Bar (left-hand
sidebar).
- Click Connect to Server, choose an authentication method, and
enter your server name and credentials.
- Browse jobs in the sidebar tree — click any job to open its full
detail.
Your password is stored via VS Code's secure SecretStorage, never
written to settings.json.
Authentication
- SQL Server Authentication — a SQL login and password.
- Windows Authentication (NTLM) — domain\user and password.
This only works if the target domain accepts NTLM; some hardened
Active Directory environments disable it in favor of Kerberos-only,
in which case SQL Server Authentication is the way to connect.
- Windows SSO (Kerberos/SSPI, no password) — not currently
available in this build. It requires a native driver that must be
compiled for your exact VS Code/Electron version; see
docs/windows-sso-setup.md in the repository if you want to enable
it yourself.
Features
- Job list with color-coded status (enabled/disabled, last run
outcome)
- Job detail in SSMS-style tabs: General, Steps, Schedules,
Alerts, Notifications, Targets, History — click a step to expand
its full detail (type, database, on-success/on-failure action,
retry settings, full command)
- Start Now, Enable/Disable, Delete — from the tree or
from the detail view
- New Job — name, description, one or more steps that can be
reordered and removed, three step types (T-SQL, Operating
system (CmdExec), PowerShell), full on success / on
failure actions per step (quit success, quit failure, go to next
step, or jump to a specific step), and a schedule (none / daily /
weekly at a specific time)
- Edit an existing job — updates the core properties and fully
replaces the steps
- Notifications — e-mail / page / Windows event log with
operator selection and a condition (on failure / success /
completion), plus "automatically delete job" (write-only — the
current setting can't be read back, so it always starts unchecked)
Known limitations
- Jobs are always assigned to the
(LOCAL) server — multi-server
topologies aren't supported.
- Schedules only support daily/weekly at a single time — monthly
schedules or multiple schedules per job aren't in the UI yet.
- Step "Advanced" options from SSMS (output file, log to table, run
as proxy user) aren't exposed yet.
Development
See CONTRIBUTING.md for running the extension locally and
packaging it into a .vsix.
| |
