Impact of a change to a custom tool box item

Question

Hi we run std 2012.  Just to be safe I'm posting this question.
We r contemplating use of a custom toolbox item for a very common update to sql.  A gac'd dll would likely run a proc in this component and i'm assuming that is not unusual for custom toolbox items.  I'm also assuming that passing one or more
ssis var params to a custom toolbox item is very doable.
Our alternatives r either a specialized sub pkg or same c# script component where/whenever this needs to run.
If the toolbox item changes does every pkg that uses it need to be visited/validated/rebuilt so that the underlying dtsx can somehow be updated?
I guess there r 3 scenarios involved:
1) passed param list changes but new params are already "known" to all of the pkgs involved anyway.
2) passed param list changes (eg new vars, different data types on existing vars) and there are new vars involved.  Clearly this would require a change to the pkg vars but does any additional step need to be taken in order for ssis to understand there
is new plumbing between the pkg and the custom component?  Or is that more of a dynamic thing at run time?  
3) change to dll is otherwise transparent to the plumbing (eg dll changes but still requires same param list) between ssis and the component. 

Answer 1

To run a stored proc with variable amount of params you can use the Execute SQL Task. I do understand that you want to speed up the development of future packages but your scenario talks about changes in the component, not the package, so I am confused,
the dtsx file gets emitted based on what the UI produces, so if you updated the DLL behind the component then the old package would not change you need to open it and re-save.
Remember, SSIS relies on static metadata, if the procedure changed the package WILL find out about that and stop working in production.
Arthur
MyBlog
Twitter