SSIS

Unlock the full potential of your SQL Server Integration Services (SSIS) environment with the Nodinite Database Monitoring Agent. This page explains how to monitor, manage, and optimize your SSIS packages and projects using the Database Monitoring Agent, providing actionable insights and rapid troubleshooting.

✅ Automatic discovery of SSIS projects and packages
✅ Proactive state evaluation and instant alerts
✅ Category-based grouping for easy management
✅ Remote actions for rapid troubleshooting and control

Learn how to monitor the execution and performance of your SQL SSIS jobs. The Database Monitoring Agent automatically creates one Resource per SSIS package, which you can monitor using suitable Monitor Views.

This page describes what's being monitored for SSIS Jobs in Nodinite using one or more role-based Monitor Views. Nodinite monitors the state based on user-defined thresholds, either global or specific. In addition, you can manage SSIS Jobs using remote commands available as Actions—helping you swiftly resolve reported problems. The implemented Remote Actions are further detailed on this page.

Example list of monitored SSIS Projects in a Monitor View

Monitoring Features

• Automatic Discovery – Projects and Packages are automatically discovered using built-in logic.
• State Evaluation – Based on the outcome of executions.
• Category-based monitoring – Group SSIS-related Resources by Categories for streamlined management.

Acquiring SSIS monitoring insights is easy from within Nodinite using Monitor Views.

State evaluation for SSIS related items

The monitored SSIS items are displayed within Nodinite as Resources. For example, if you have 1 SSIS database with 4 master projects with 3 projects each, you will have 17 Resources in Nodinite.

• The name of the Resources comes from the composition of the package folder and project names, providing a unique naming scheme.

• All monitored SSIS items belong to one of the following 'SSIS' Categories:

  Category	Description
  SSIS Instance	Make sure the SSIS database itself is really available
  SSIS Master Project	Master packages group projects and facilitate monitoring and management
  SSIS Project	Make sure the individual projects are executing successfully

  
  List of SSIS related categories as the filter option in a Monitor View

• The Application name is the Display Name from the user-defined configuration:
  
  Example of an Application Path for SSIS monitoring.

Each item (presented in Nodinite as a Resource) is evaluated with a state (OK, Warning, Error, Unavailable).

From within Nodinite, you can reconfigure the state evaluation on the Resource level using the Expected State feature.

Note

Depending on the user-defined synchronization interval set for the Database Monitoring Agent, there might be a delay before Nodinite Web Client/Monitor Views reflects the change. Click the Sync All button (or use the dropdown for individual agent selection) to force Nodinite to request a resynchronization.

Option to force Nodinite to request a resynchronization with the monitoring agent.

---

Global Configuration

Click the SSIS tab to manage SSIS monitoring options.

Example of the SSIS configuration tab.

• Enable SSIS Monitoring – When checked, SSIS Monitoring is enabled.
• Description – User-friendly description for this SSIS configuration.

Specific Projects

Click the Add button to add specific settings for named SSIS projects:

Example of adding specific SSIS project settings.

From within the modal, you can manage basic configurations and also opt to provide time-based options.

First, in the Configuration tab, pinpoint details for the specific SSIS project:

Example of the configuration tab for a specific SSIS project.

Set the following properties:

• Enable monitoring of specific SSIS Project – Enabled when checked
• SSIS Folder Name – The name of the specific SSIS Folder
• SSIS Project Name – The name of the specific SSIS Project
• Clear Date-Time – Clear/Ignore all warning(s) and error(s) that occurred before this time; events with an older date-time will not be evaluated/displayed __

SSIS Instance

For the SSIS Instance category, the monitored state evaluates as described in the table below:

SSIS Master Project

For the SSIS Master Project category, the monitored state evaluates as described in the table below:

SSIS Project

For the SSIS Project category, the monitored state evaluates as described in the table below:

	State	Status	Description	Actions
	Unavailable	Resource not available	Evaluation of the 'SSIS Project' is not possible either due to network or security-related problems	Review prerequisites
	Error	Error state raised	SSIS executions that fail will render state 'Error'	View Executions Edit partial interval Clear
	OK	Online	Enabled and running	View executions Edit partial interval Clear

Tip

The System Administrator can override the Monitoring state using the Expected State feature on the Resource within Nodinite.

Example of available actions for SSIS monitoring.

View executions for SSIS Projects

View the last n runs of the selected SSIS package. The number of available logs can be set from within SQL Server Management Studio (SSMS). Please review the retention window user guide for additional details.

Example of viewing SSIS execution history.

If used on a SSIS Project, it shows all executed packages within that project. You can expand each package to get an overview of the run and also see the message log for it.

Example of viewing all executed packages within a project.

To conserve bandwidth and improve performance, the list is presented using pagination.

The list can be updated by simply clicking the Reload button in the upper right corner, without the need to reopen the form.

The Default values are set using Remote Configuration. These global settings can be overridden by specific SSIS using the 'Edit SQL SSIS Configuration' action.

The following properties can be set:

• Enable feature Monitoring of SSIS Packages
• Description, a user-friendly description for SSIS
• Specific Projects, Clear Date Time per SSIS Project to only evaluate status from this project's packages after this date and time

Clear

You can have old failed runs removed by applying a filter on old runs. The time for this filter is the point in time when you either click on the Clear action, or by manually editing the value in the global configuration. For a selected SSIS job, simply click on the Action button and then click on the Clear menu item within the 'Control Center' section.

Filter old runs, using the 'Clear' action.

You will then be prompted to confirm the intent to proceed with the operation:

Here's an example of the 'Clear' prompt.

Next, a modal presents the result of the operation:

Here's an example of a successful clear operation.

Save

You must click 'Save' or 'Save and close' for changes to persist. The new settings/thresholds are evaluated on the next synchronization.

Here's an example of the Save options.

Note

Depending on the synchronization interval set for the agent, there might be a delay before the Web Client reflects the change. You can force the agent to synchronize the Configuration for all Nodinite Monitoring Agents.

Save and close saves and closes the dialogue.
Cancel closes the dialogue without saving any changes.

---

Next Step

Add or manage Monitor View

Related Topics

Database Monitoring Agent
SQL Categories
Resources
Monitoring Agents
Monitor Views