SQL Agent jobs
Keep BizTalk operations stable by monitoring SQL Agent jobs that support MessageBox, tracking, and maintenance behavior. This Health Check helps you detect failed or misconfigured jobs early and document expected behavior for customized environments.
Example of the SQL Agent jobs resource in a Monitor View, where state, category, application, and log text expose job-related deviations.
Category Name = "Health Check"
Resource Name = "SQL Agent jobs"
What is evaluated for SQL Agent jobs?
Nodinite evaluates BizTalk-related SQL Agent jobs against expected behavior. Jobs that are disabled by design are accepted, while unexpected disabled jobs, failed runs, and stopped continuous jobs are reported.
The evaluated states are summarized below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of SQL Agent jobs is not possible due to network, security, or SQL connectivity issues | Review Prerequisites | |
| Error | One or more jobs require immediate attention | At least one monitored job deviates from expected configuration or execution outcome | Details Edit |
|
| Warning | One or more warning events detected | Aggregate warning conditions exist and require operator review | Details Edit |
|
| OK | All monitored jobs align with expected behavior | No critical deviations detected for monitored SQL Agent jobs | Details Edit |
Tip
You can tune state handling for this resource with Expected State if your operations policy requires custom behavior.
What remote actions are available?
- Details - Inspect each monitored SQL Agent job and its latest execution outcome
- Edit - Enable or disable monitoring and configure per-job overrides
Details
Start with the Details action to view all monitored jobs, expected state, actual state, last run outcome, and notes.
Example of the Details modal showing job count, SQL instances, expected versus actual state, and operator guidance in Notes.
When you expand a row, you get deeper operational context such as SQL description, monitoring override description, schedule intent, and what to monitor.
Example of an expanded Details entry with additional troubleshooting context for one SQL Agent job.
Edit
Use Edit when you need richer control than global settings. This is the preferred way to manage SQL Agent job-specific behavior.
Example of the Edit modal where you can enable monitoring, add per-job overrides, map built-in jobs to discovered SQL jobs, and save configuration changes.
Per-job override workflow
- Click Add override to create a new entry.
- Select the discovered Job name.
- Select the Built-in job mapping when your SQL Agent job has a custom name.
- Set options such as Enabled and Exclude from monitoring.
- Add a Description to document why this configuration change exists.
- Click Save to persist changes.
Note
Mapping built-in jobs to discovered jobs is especially useful in environments where SQL Agent job names were changed.
Remote Configuration
You can also configure SQL Agent jobs from Remote Configuration.
Example of the Remote Configuration tab with SQL Agent jobs settings and per-job override entries.
Supported configuration actions:
- Toggle monitoring on or off.
- Manage specific configurations using the Edit modal (preferred richer UI).