Export (0) Print
Expand All

Enable Logging for Package Execution on the SSIS Server

This procedure describes how to set or change the logging level for a package when you execute a package that you have deployed to the Integration Services server. The logging level you set when you execute the package overrides the package logging you configure using SQL Server Data Tools (SSDT). See Enable Package Logging in SQL Server Data Tools for more information.

You can specify the logging level by using one of the following methods. This topic covers the first method.

  • Configuring an instance of a package execution by using the Execute Package dialog box

  • Setting parameters for an instance of an execution by using the catalog.set_execution_parameter_value (SSISDB Database)

  • Configuring a SQL Server Agent job for a package execution by using the New Job Step dialog box.

To set the logging level for a package by using the Execute Package dialog box

  1. In SQL Server Management Studio, navigate to the package in Object Explorer.

  2. Right-click the package and select Execute.

  3. Select the Advanced tab in the Execute Package dialog box.

  4. Under Logging level, select the logging level. See the table below for a description of available values.

  5. Complete any other package configurations, then click OK to run the package.

The following logging levels are available.

Logging Level

Description

None

Logging is turned off. Only the package execution status is logged.

Basic

All events are logged, except custom and diagnostic events. This is the default value.

Performance

Only performance statistics, and OnError and OnWarning events, are logged.

The Execution Performance report displays Active Time and Total Time for package data flow components. This information is available when the logging level of the last package execution was set to Performance or Verbose. For more information, see Reports for the Integration Services Server.

The catalog.execution_component_phases view displays the start and end times for the data flow components, for each phase of an execution. This view displays this information for these components only when the logging level of the package execution is set to Performance or Verbose.

Verbose

All events are logged, including custom and diagnostic events.

An example of a diagnostic event, is the DiagnosticEx event. Whenever an Execute Package task executes a child package, it logs this event. The event message consists of the parameter values passed to child packages

The value of the message column for DiagnosticEx is XML text. . To view the message text for a package execution, query the catalog.operation_messages (SSISDB Database) view.

Note Note

Custom events include those events that are logged by Integration Services tasks. For more information, see Custom Messages for Logging.

The catalog.execution_data_statistics view displays a row each time a data flow component sends data to a downstream component, for a package execution. The logging level must be set to Verbose to capture this information in the view.

Community Additions

ADD
Show:
© 2014 Microsoft