Extending Packages with Custom Objects

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

• Developing Custom Objects for Integration Services
  Discusses the custom objects that can be created for Integration Services, and summarizes the essential steps and settings.

• Persisting Custom Objects
  Discusses the default persistence of custom objects, and the process of implementing custom persistence.

• Building, Deploying, and Debugging Custom Objects
  Discusses the common approaches to building, deploying and testing the various types of custom objects.

• Developing a Custom Task
  Describes the process of coding a custom task.

• Developing a Custom Connection Manager
  Describes the process of coding a custom connection manager.

• Developing a Custom Log Provider
  Describes the process of coding a custom log provider.

• Developing a Custom ForEach Enumerator
  Describes the process of coding a custom enumerator.

• Developing a Custom Data Flow Component
  Discusses how to program custom data flow sources, transformations, and destinations.

Reference

• Integration Services Error and Message Reference
  Lists the predefined Integration Services error codes with their symbolic names and descriptions.

Related Sections

• 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.

See Also

Reference

Comparing Scripting Solutions and Custom Objects

Concepts

SQL Server Integration Services