Export (0) Print
Expand All

Managing the Integration Services Service

Updated: 15 September 2007

SQL Server 2005 Integration Services (SSIS) includes the Integration Services service, a Windows service for managing Integration Services packages.

The Integration Services service is not required to create, save, and run Integration Services packages.

When you install the Integration Services component of SQL Server 2005, the Integration Services service is also installed. 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.

You can only install a single instance of the Integration Services service on a computer. The service is not specific to the instance. You connect to the service by using the name of the computer on which the service 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 that are stored in the msdb database in a local, default instance of 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.

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. 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.

Release History

15 September 2007

New content
  • Described how to connect to Integration Services service.
  • Explained that, to manage the msdb database on remote or multiple instances, you must modify the default configuration file.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft