If you find that the components provided in Integration Services do not meet your requirements, you can extend the power of Integration Services by coding your own extensions. You have two discrete options for extending your packages: you can write code within the powerful wrappers provided by the Script task and the Script component, or you can create custom Integration Services extensions from scratch by deriving from the base classes provided by the Integration Services object model.
This section explores the more advanced of the two options — extending packages with custom objects.
When your custom Integration Services solution requires more flexibility than the Script task and the Script component provide, or when you need a component that you can reuse in multiple packages, the Integration Services object model lets you build custom tasks, data flow components, and other package objects in managed code from the ground up.

In This Section

Reference

Related Sections
-
Developer's Guide (Integration Services)
-
Introduces Integration Services programming concepts.
-
Extending Packages with Scripting
-
Discusses how to extend the control flow by using the Script task, or extend the data flow by using the Script component.
-
Building Packages Programmatically
-
Describes how to create, configure, run, load, save, and manage Integration Services packages programmatically.
-
Programming Samples
-
Lists and describes the Integration Services programming samples that are available as an optional installation component.
-
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 or TechNet:
For automatic notification of these updates, subscribe to the RSS feeds available on the page.
|

See Also