Integration Services Service (SSIS Service)

The topics in this section discuss the Integration Services service, a Windows service for managing Integration Services packages. This service is not required to create, save, and run Integration Services packages. SQL Server 2012 supports the Integration Services service for backward compatibility with earlier releases of Integration Services.

Ważne:
You do use the Integration Services service to run packages outside of the design environment. To use the dtexec command prompt utility to run packages, you need to install the Integration Services service.

Starting in SQL Server 2012, Integration Services stores objects, settings, and operational data in the SSISDB database for projects that you’ve deployed to the Integration Services server using the project deployment model. The Integration Services server, which is an instance of the SQL Server Database Engine, hosts the database. For more information about the database, see SSIS Catalog. For more information about deploying projects to the Integration Services server, see Deploy Projects to Integration Services Server.

Management Capabilities

The Integration Services service is a Windows service for managing Integration Services packages. The Integration Services service is available only in SQL Server Management Studio.

Running the Integration Services service provides the following management capabilities:

• Starting remote and locally stored packages

• Stopping remote and locally running packages

• Monitoring remote and locally running packages

• Importing and exporting packages

• Managing package storage

• Customizing storage folders

• Stopping running packages when the service is stopped

• Viewing the Windows Event log

• Connecting to multiple Integration Services servers

Startup Type for Integration Services Service

The Integration Services service is installed when you install the Integration Services component of SQL Server. By default, the Integration Services service is started and the startup type of the service is set to automatic. The service must be running to monitor the packages that are stored in the SSIS Package Store. The SSIS Package Store can be either the msdb database in an instance of SQL Server or the designated folders in the file system.

The Integration Services service is not required if you only want to design and execute Integration Services packages. However, the service is required to list and monitor packages using SQL Server Management Studio.

Related Tasks

• Set the Properties of the Integration Services Service

• View Events for the Integration Services Service

Related Content

Stay Up to Date with Integration Services For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the Integration Services page on MSDN: Visit the Integration Services page on MSDN For automatic notification of these updates, subscribe to the rss feeds available on the page.