Perry,
I couldn't agree more that code-reuse is the single biggest stumbling block at the moment in SSIS - and the situation isn't any better in the June CTP either I'm afraid. I have it on good authority that this is one of the major things they are looking at improving in vNext though.
My solution to this problem (in the scenario of logging) is two-fold
1) Encapsulate the Execute SQL task that does the logging in another package - all you do is pass it the values that it is going to log using parent package configurations. I have got this working and it works very well (except that it is slow when running in the designer with debugging).
2) Have a template package containing all of the pre-built event handlers (whether these are Execute SQL tasks or Execute Package tasks) and build all of your packages on top of this template. The logging is then something you don't even have to think about (theoretically anyway).
-Jamie
I couldn't agree more that code-reuse is the single biggest stumbling block at the moment in SSIS - and the situation isn't any better in the June CTP either I'm afraid. I have it on good authority that this is one of the major things they are looking at improving in vNext though.
My solution to this problem (in the scenario of logging) is two-fold
1) Encapsulate the Execute SQL task that does the logging in another package - all you do is pass it the values that it is going to log using parent package configurations. I have got this working and it works very well (except that it is slow when running in the designer with debugging).
2) Have a template package containing all of the pre-built event handlers (whether these are Execute SQL tasks or Execute Package tasks) and build all of your packages on top of this template. The logging is then something you don't even have to think about (theoretically anyway).
-Jamie