Integration Services Architecture
Microsoft SQL Server 2005 Integration Services (SSIS) consists of four key parts: the Integration Services service, the Integration Services object model, the Integration Services runtime and the run-time executables, and the Data Flow task that encapsulates the data flow engine and the data flow components.
The following diagram shows the relationship of the parts.
.gif "Integration Services architecture")
Developers who access the Integration Services object model from custom clients or write custom tasks or transformations can write code by using any common language runtime (CLR) compliant language. For more information, see Integration Services Programming.
Integration Services Service
The Integration Services service, available in SQL Server Management Studio, monitors running Integration Services packages and manages the storage of packages.
For more information, click one of the following topics:
Introducing SQL Server Management Studio
Integration Services Object Model
The Integration Services object model includes managed application programming interfaces (API) for accessing Integration Services tools, command-line utilities, and custom applications.
For more information, click one of the following topics:
Integration Services Programming
Integration Services Tools and Utilities
Integration Services Runtime
The Integration Services runtime saves the layout of packages, runs packages, and provides support for logging, breakpoints, configuration, connections, and transactions. The Integration Services run-time executables are the package, containers, tasks, and event handlers that Integration Services includes, and custom tasks.
For more information, click one of the following topics:
Integration Services Containers
Integration Services Event Handlers
Microsoft.SqlServer.Dts.Runtime
Integration Services Data Flow
The Data Flow task encapsulates the data flow engine. The data flow engine provides the in-memory buffers that move data from source to destination, and calls the sources that extract data from files and relational databases. The data flow engine also manages the transformations that modify data, and the destinations that load data or make data available to other processes. Integration Services data flow components are the sources, transformations, and destinations that Integration Services includes. You can also include custom components in a data flow.
For more information, click one of the following topics:
Microsoft.SqlServer.Dts.Pipeline.Wrapper
Change History
| Release | History |
|---|---|
17 July 2006 |
|
See Also
Concepts
Typical Uses of Integration Services
Integration Services Overview
SQL Server Integration Services
Other Resources
Integration Services Objects and Concepts