Share via

Manage the Integration Services Service

  • Article

Important

This topic discusses the Integration Services service, a Windows service for managing Integration Services packages. SQL Server 2012 supports the service for backward compatibility with earlier releases of Integration Services. Starting in SQL Server 2012, you can manage objects such as packages on the Integration Services server.

When you install the Integration Services component of SQL Server, the Integration Services service is also installed. By default, the Integration Services service is started and the startup type of the service is set to automatic. However, you must also install SQL Server Management Studio to use the service to manage stored and running Integration Services packages.

Note

You cannot connect to an instance of the SQL Server 2005Integration Services service from the SQL Server 2008 version of Management Studio. That is, in the Connect to Server dialog box, you cannot enter the name of a server on which only the SQL Server 2005 version of the Integration Services service is running. However, you can edit the configuration file for the service and thereby manage packages that are stored in an instance of SQL Server 2005 from the SQL Server 2008 version of Management Studio. For more information, see Configuring the Integration Services Service (SSIS Service).

You can only install a single instance of the Integration Services service on a computer. The service is not specific to a particular instance of the Database Engine. You connect to the service by using the name of the computer on which it is running.

You can manage the Integration Services service by using one of the following Microsoft Management Console (MMC) snap-ins: SQL Server Configuration Manager or Services. Before you can manage packages in SQL Server Management Studio, you must make sure that the service is started.

By default, the Integration Services service is configured to manage packages in the msdb database of the instance of the Database Engine that is installed at the same time as Integration Services. If an instance of the Database Engine is not installed at the same time, the Integration Services service is configured to manage packages in the msdb database of the local, default instance of the Database Engine. To manage packages that are stored in a named or remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file for the service. For more information, see Configuring the Integration Services Service (SSIS Service).

By default, the Integration Services service is configured to stop running packages when the service is stopped. However, the Integration Services service does not wait for packages to stop and some packages may continue running after the Integration Services service is stopped.

If the Integration Services service is stopped, you can continue to run packages using the SQL Server Import and Export Wizard, the SSIS Designer, the Execute Package Utility, and the dtexec command prompt utility (dtexec.exe). However, you cannot monitor the running packages.

By default, the Integration Services service runs in the context of the NETWORK SERVICE account.

The Integration Services service writes to the Windows event log. You can view service events in SQL Server Management Studio. You can also view service events by using the Windows Event Viewer.

To set properties of Integration Services service using the Services snap-in

To view service events for Integration Services service

See Also

Integration Services Service (SSIS Service)
Configuring the Integration Services Service (SSIS Service)
SQL Server Import and Export Wizard
dtexec Utility
Execution of Projects and Packages