Using Integration Services with Other Applications
New: 14 April 2006
If you need to create packages dynamically, or to manage and execute Integration Services packages outside the development environment, you can manipulate packages programmatically. You can use the Integration Services object model to write code that creates and configures a new package, or loads and executes a saved package, in any managed programming language. You can also load the output of a package's data flow directly from memory into your custom application.
For more information, see Building Packages Programmatically.
Note
When working with packages programmatically, it is important to understand the limitations and licensing issues related to running packages on the local computer or on the remote server. For more information, see Understanding the Differences between Local and Remote Execution.
Working with Packages from Other Applications
Using the extensive Integration Services object model, you can:
- Build and configure packages. Create a new package one task and component at a time, and then save it to your preferred storage location. For more information, see Building Packages Programmatically.
- Enumerate saved packages. Loop through existing packages to check whether an individual package or folder exists. For more information, see Enumerating Available Packages Programmatically.
- Load and execute. Open a saved package, optionally reconfigure it, and then run the package. You can also load the output of the package's data flow into your application directly from memory. For more information, see Loading and Running a Local Package Programmatically, Loading and Running a Remote Package Programmatically, and Loading the Output of a Local Package.
- Managed saved packages and folders. Remove or add packages, and create, rename, or remove folders. For more information, see Managing Packages and Folders Programmatically.
See Also
Other Resources
Using Integration Services with Other SQL Server Features