You are adding a new capability to several dozen SQL Server Integration Services (SSIS) packages.
The new capability is not available as an SSIS task. Each package must be extended with the same new
capability.
You need to add the new capability to all the packages without copying the code between packages.
What should you do?
A.
Use the Expression task.
B.
Use the Script task.
C.
Develop a custom task.
D.
Use the Script component,
E.
Develop a custom component.
Explanation:
http://msdn.microsoft.com/en-us/library/ms135965.aspx
http://msdn.microsoft.com/en-us/library/ms345161.aspx
This is where SSIS custom tasks become useful. When you want to use the same script task in several different places or packages then it is time to promote it to a custom task. This provides several benefits.
Code duplication is eliminated.
The need for a script task goes away and is replaced by a reusable task.
A custom task is easier to use in packages then script tasks.
The custom task can access functionality that is difficult or impossible to do inside a script task.