01 Architecture Of Integration Services


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Developing Project Data Sources and Package ConnectionsBecause the main purpose of SSIS is to move data from sources to destinations, the nextmost important step is to add the pointers to these sources and destinations. These pointersare called data sources and connections. Data sources are stored at the project level and arefound in Solution Explorer under the logical folder named Data Sources. Connections, on theother hand, are defined within packages and are found in the Connection Managers pane atthe bottom of the Control Flow or Data Flow tab. Connections can be based on project datasources or can stand alone within packages. The next sections walk you through the uses andimplementation of project data sources and package connections.
  • These workflow elements might involve:running a stored proceduremoving a file from an FTP server to a destination foldersend an e-mail message when an error occursPackages also contain connections to data sources and data destinations. You set up these connections to connect to different external systems such as databases, files, File Transfer Protocol (FTP) servers, Simple Mail Transfer Protocol (SMTP) servers, and so on. Connections are used for the SSIS data processing engine (called the data flow) as well as the workflow engine (called the control flow).
  • The objects that compose an Integration Services package include the following:The package itself The package, the unit of work that is retrieved, executed, and saved, and the most important Integration Services object.For more information, see Integration Services Packages.Control flow elements The control flow elements—tasks and containers—for building the control flow in a package. Control flow elements prepare or copy data, interact with other processes, or implement repeating workflow. Precedence constraints sequence the control flow elements into an ordered control flow and specify the conditions for executing tasks or containers. For more information, see Control Flow Elements.Data flow components The data flow components—sources, transformations, and destinations—for building data flows in a package that extract, transform, and load data. Paths sequence the data flow components into an ordered data flow. For more information, see Data Flow Elements.Connection managers The connection managers that connect to different types of data sources to extract and load data. For more information, see Integration Services Connections.Variables The variables that can be used in expressions to dynamically update column values and property expressions, control execution of repeating control flows, and define the conditions that precedence constraints apply. For more information, see Integration Services Variables.Event handlers The event handlers that run in response to the run-time events that packages, tasks, and containers raise. For more information, see Integration Services Event Handlers.Log providers The log providers that support logging of package run-time information such as the start time and the stop time of the package and its tasks and containers. For more information, see Integration Services Log Providers.
  • ×