SQLJobCommander:Documentation: Difference between revisions
More actions
No edit summary |
|||
| Line 138: | Line 138: | ||
* More to come on this topic. | * More to come on this topic. | ||
=== <span style="text-transform: uppercase;">Main Window</span> === | === <span style="text-transform: uppercase;">Main Window</span> === | ||
* More to come on this topic. | |||
=== <span style="text-transform: uppercase;">Preferences</span> === | |||
* More to come on this topic. | * More to come on this topic. | ||
=== <span style="text-transform: uppercase;">Connecting to a SQL Server® Instance</span> === | === <span style="text-transform: uppercase;">Connecting to a SQL Server® Instance</span> === | ||
Revision as of 00:02, 16 June 2026
Home | Download from the MS Store | Download from Brentec | Features/Visual Tour | Requirements | Documentation | Change Log | Roadmap
Introduction
What is SQL Job Commander?
SQL Job Commander is a powerful SQL Server® Agent job management tool that delivers familiar SSMS functionality while adding unique capabilities for enhanced job manipulation and control.
Here are the key features of SQL Job Commander:
- Purpose-built for SQL Server® Agent job management over the traditional SQL Server® Management Studio (SSMS).
- Intuitive, feature-rich environment including the ability to copy jobs between instances and scripting multiple jobs concurrently.
- All-in-one interface for managing multiple SQL Server® Agent instances.
- Per-instance metrics showing succeeded, failed, cancelled, and actively running jobs along with the instance job success rate.
- Clear, per-job running indicator with threshold breach visualization.
- Per-job coloring indicative of job type.
- Per-instance job filtering for those larger estates, finding a job or group of jobs quickly.
- Full job history showing executions by status and the most recent 100 executions by duration visualizations.
- Script output with full T-SQL syntax highlighting.
Download & Installation
Overview
SQL Job Commander is a desktop application for managing and executing SQL Server Agent jobs. It is available in two distribution packages: a standard (framework-dependent) build and a self-contained build.
System Requirements
| Requirement | Standard Build | Self-Contained Build |
|---|---|---|
| .NET 8 Desktop Runtime | Required | Not required (bundled) |
| Operating System | Windows | Windows |
Download Packages
There are 2 download options available depending on your environment.
1. Standard Build (Framework-Dependent)
| Field | Value |
|---|---|
| Filename | sjc-0.1.2606.0.zip
|
| SHA256 Hash | 1eaf980d5bbd20bf144878a0e5dc3eab5789f23229d32c8eb6b454ebcac31416
|
| Features Expiry | January 1, 2027 |
| Download | Download SQL Job Commander |
| Virus Scan | Verify on VirusTotal |
2. Self-Contained Build
| Field | Value |
|---|---|
| Filename | sjc-0.1.2606.0-sc.zip
|
| SHA256 Hash | a99ca21b3a633eea465d882062df07a64bafa0df53a096d2729a30d23f7373c4
|
| Features Expiry | January 1, 2027 |
| Download | Download SQL Job Commander (Self-Contained) |
| Virus Scan | Verify on VirusTotal |
Installation
- Download the appropriate
.zipfile for your environment (see above). - Verify the file integrity using the SHA256 hash provided (see Verifying the Download below).
- Extract the contents of the
.zipfile to a folder of your choice. - If using the standard build, ensure the .NET 8 Desktop Runtime is installed before launching.
- Run
SQLJobCommander.exefrom the extracted folder.
Verifying the Download
To confirm your download has not been tampered with, verify the SHA256 hash of the .zip file before extracting it.
Using PowerShell (Windows):
Get-FileHash .\sjc-0.1.2606.0.zip -Algorithm SHA256
Compare the output against the SHA256 hash listed in the download table above. Alternatively, you can submit the hash directly to VirusTotal using the links provided.
Feature Expiry Notice
Which Build Should I Choose?
| Scenario | Recommended Build |
|---|---|
| .NET 8 Desktop Runtime is already installed | Standard Build (smaller download) |
| Deploying to a machine where installing runtimes is restricted or to get up and running quicker | Self-Contained Build |
| Unsure | Self-Contained Build |
Licensing
- More to come soon on this topic.
Release Notes/Changelog
Roadmap
Getting Started
About
- More to come on this topic.
Main Window
- More to come on this topic.
Preferences
- More to come on this topic.
Connecting to a SQL Server® Instance
- More to come on this topic.
Dashboard
- More to come on this topic.
Job Monitor
The Job Monitor component serves as a comprehensive at-a-glance view of all SQL Agent jobs for each connected SQL Server® instance within SQL Job Commander.
Much like SQL Server® Management Studio's Job Activity Monitor, it displays a grid of every job on the connected instance, surfacing key details such as job name, enabled status, current execution status (running, idle, cancelled, or failed), last run outcome, last run date and time, next scheduled run, and the executing step — all in one unified panel. Users can quickly identify stuck, failed, or long-running jobs without needing to query system tables manually, and can take immediate action by right-clicking a job for further actions directly from the grid.
Each Job Monitor supports sorting and filtering, allowing operators to zero in on jobs matching specific criteria — such as all currently running jobs or all jobs that failed within the last cycle. Designed for both at-a-glance monitoring and rapid triage, the Job Monitor transforms what would otherwise be a fragmented, query-heavy workflow into a streamlined, visual operations hub that keeps database administrators firmly in control of their job pipeline.
Right-clicking a job will provide a context menu with the following options:
| Option | Description |
| Create a New Job | A new window will be presented to create a new job. |
| Start Job at Step | A dialog will appear showing all job steps, allowing the operator to choose the job step at which point to start the job. This option is disabled should the selected job not contain any steps. |
| Stop Job | Stops the currently selected running job. |
| View History | Shows the complete execution history for a selected SQL Agent job in a new window. This option is disabled should job history be non-existent for the selected job. |
| Delete History | This option is disabled should job history by non-existent for the selected job, or, if the job is multi-server in nature. |
| Scripting Actions | A dialog is shown allowing many different scripting options. Toggle the appropriate checkboxes and click OK to generate the desired scripts. |
| Copy Job to Another Instance | This option is disabled if there are fewer than two (2) instance connections. |
| Enable | Enables the selected job. This option is disabled if the current selected job is already enabled. |
| Disable | Disables the selected job. This option is disabled if the current selected job is already disabled. |
| Rename | A dialog will appear asking for the new name of the selected job. |
| Delete | A dialog will appear asking for confirmation before deleting the selected job. Additionally, there are options to Keep Unused Schedules and to Script as Create before confirming the deletion. |
| Properties | A new window is presented showing all of the job properties, ready to be modified if necessary. When viewing job properties of a multi-server job on a target server, job properties will be read-only, and must be modified on the master. |
Session Log
The Session Log tab displays a running record of activity and events that occur during your session in SQL Job Commander. Log entries are colour-coded by severity and can be searched, filtered, copied, and cleared.
Log Entry Types
Each entry in the session log is assigned one of the following severity levels:
| Severity | When it appears |
|---|---|
| Critical | A serious error or failure that requires attention |
| Warning | A non-fatal issue or notable event worth reviewing |
| Informational | General activity and status updates |
A live count of entries for each severity level is displayed at the top of the log.
Searching and Filtering
Search Box
Type in the search box to filter the log in real time. The search checks all columns — date/time, instance, and message — and shows only entries that contain your search text.
Press ESC to clear the search box.
Searching by Instance
To filter by a specific instance name, wrap the instance name in curly braces:
{MyInstanceName}
Only entries whose Instance exactly matches the value inside the braces will be shown. The search is not case-sensitive.
While you are still typing the opening brace and have not yet closed it with }, all entries remain visible.
Filter Checkboxes
Click the Expand/collapse filter pane button to open the filter panel. The following checkboxes are available:
| Checkbox | Effect |
|---|---|
| Hide critical entries | Hides all critical-severity entries |
| Hide warning entries | Hides all warning-severity entries |
| Hide informational entries | Hides all informational entries |
| Hide heartbeat success messages | Hides routine heartbeat messages from the log |
Checkboxes and the search box work together — only entries that pass all active filters are shown.
Filter Status
Below the data grid, a status label shows how many entries are currently visible:
- If filters are active, it shows how many entries are displayed out of the total, highlighted in red.
- If no filters are active, it shows the total number of entries.
Clearing Filters
Click Clear selected filters to reset the search box and uncheck all filter checkboxes, returning the log to its unfiltered state.
Toolbar Buttons
| Button | Description |
|---|---|
| Expand/collapse filter pane | Opens or closes the filter panel |
| Clear selected filters | Removes all active filters and search text |
| Size all columns to fit contents | Automatically resizes all columns to fit their content |
| Copy visible log entries to clipboard | Copies the currently visible log entries to your clipboard as tab-delimited text, including column headers. The button briefly shows a checkmark to confirm the copy was successful. |
| Clear entire log | Clears all entries from the session log. A single warning entry is added automatically to record that the log was manually cleared. |
Copying the Log
The Copy visible log entries to clipboard button copies everything currently visible in the grid (based on your active filters) to your clipboard. The copied data includes the following columns:
- Date/Time
- Instance
- Message
You can paste this directly into a spreadsheet or text editor. Column headers are included in the copied output.
Keyboard Navigation
| Key | Action |
|---|---|
| Escape | Clear the search box |