Quick Manage Form for SQL Agent Job

SQL Agent Quick Manage

In Object Explorer, right-click a job under SQL Server Agent > Jobs and select Quick Manage. The command is available only in a job's context menu.

Quick Manage opens in the SSMS document area alongside query tabs, titled Job name - Quick Manage. Reopening the same job on the same server and authentication identity activates its existing tab without replacing drafts. Different jobs can remain open simultaneously. Tabs are session-only and are not restored when SSMS restarts.

The tab shows the job name and server, current status, schedules, and the latest execution result. Details load asynchronously. The Steps tab keeps the step list beside the command editor. Job details combines description, category, creation/modification dates, job ID, and schedules. The Execution history tab shows up to the latest 100 completed runs in a tree, newest first. Expand a run to inspect its step attempts, including retries; select any run or step to read its full recorded message, outcome, start time, and duration. A compact header keeps job identity, status badges, and actions together, followed by a single-line last/next execution strip. Narrow or split document groups scroll the content to keep actions reachable.

Common tasks

• Start / Stop requests a job start or stop through SQL Server Agent. Starting uses the job's configured starting step and its saved commands.
• Enable / Disable changes the job's enabled flag. Individual schedules and other job properties are not changed.
• Refresh or F5 reloads job details, schedules, steps, and current status while retaining unsaved command drafts. It does not reload execution history.
• Refresh history, inside Execution history, reloads execution records and status without reloading step commands, schedules, or job details. It preserves the selected history entry and expanded runs.
• Select a step to inspect its command, subsystem, database, and success/failure routing. A flag marks the configured starting step, which may be a step other than step 1. The marker follows server changes on refresh.
• Edit the command and select Save step to persist that step only. Discard restores the saved command.
• Format SQL applies the existing Axial SQL Tools formatter to a T-SQL command. Formatting is an editable, undoable change and is not saved automatically.

The editor uses the font family and size configured for SSMS's T-SQL editor when the tab opens, with Consolas 10pt as a fallback. Ctrl+wheel changes the zoom for the current Quick Manage tab. The editor includes syntax highlighting, line numbers, search, and undo/redo. Non-SQL commands are not passed to the T-SQL formatter. Commands that the formatter cannot parse, including some SQL Agent token expressions, remain unchanged if formatting fails.

Schedules appear in Job details, with SQL Server's human-readable descriptions from msdb.dbo.sp_help_jobschedule @include_description = 1, including frequency and active-date information.

Execution history loads asynchronously once when Quick Manage opens. After that, only Refresh history reloads the execution records; the top Refresh button, F5, and refreshes following job actions leave the history tree intact. The most recent run is initially expanded; Refresh history preserves the selected history entry and expanded runs when those records are still available. If a history refresh fails, previously loaded history stays visible with a warning. SQL Server Agent retention determines how many of the 100 runs and step messages are available. In-progress steps are not attached to a completed run.

Status and edits

Job information loads when the window opens and refreshes after job actions. Use Refresh or F5 to update job information and status, and Refresh history for execution records; there is no timed refresh. Refreshing preserves unsaved command drafts. Command edits, including formatting, show Unsaved changes in bold red and enable Save step and Discard. Closing with unsaved changes asks whether to discard them. Refresh failures are shown in the window instead of replacing the last successful snapshot with empty data.

Before a command is saved, Quick Manage checks that the same step still exists and that its command, subsystem, and database have not changed on the server. A conflict keeps the local draft and requires reconciling it with the current server version. A save changes only the command through msdb.dbo.sp_update_jobstep; it does not recreate the job or its steps.

Dates and times are shown in the SQL Server's local time. SQL Agent's cached next-run values can lag schedule edits, so the next-run time is an estimate. Job status is a snapshot, and a start or stop request can take time to appear in the next refresh.

Quick Manage uses the selected Object Explorer connection and does not elevate permissions. Viewing full commands and safely saving edits requires SELECT access to msdb.dbo.sysjobsteps and msdb.dbo.sysjobs_view; execution messages use msdb.dbo.sysjobhistory. Job actions also require the usual SQL Server Agent permissions. Sysadmin accounts satisfy these requirements. Permission failures and unavailable Agent status are reported in the window.