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:
References:
http://msdn.microsoft.com/en-us/library/ms135965.aspx
http://msdn.microsoft.com/en-us/library/ms345161.aspx
why not D?
0
0
Because after you develop of custom task,
it’s apperaring like any other native task
in SSIS toolbox and you can use it in all
your projects.
Cozyroc already had developed a lot of custom task
you can purchaise and extend ssis capabilities.
http://www.cozyroc.com/
0
0
D.
Use the Script component, is right.
0
0
C) Custom task as the question is referencing capability not available as a task
0
0
Task vs Component. Choose component for this stupid reason that the questions says the capability is not otherwise available as an ssis task. Of course the capabilities of a component aren’t available to task too, but again this is why the microsoft questions suck.
By the way, the obvious difference between a task and component is that a component works on data flows on a row by row basis and in the aggregate while a task is a control flow item that can work on the entire data set, moving things around, or on a row by row basis so long as it doesn’t then have to feed into another component. This is the knowledge this stupid question really should have tested if it wasn’t written by morons.
Custom vs. Script. Custom can be used over many packages as it just becomes a new component on the ssis toolbox Scripts are only good in the project you made them in unless you cut and paste the code elsewhere.
1
0