OOAD concepts in SSIS

Hi,

Has anyone tried to explore the possibility of inheritence and instantiation within SSIS? For example, a derived column component being used in multiple data flow component or a same lookup component used multiple times in different data flow components.

Something very similiar to defining a class and instantiating it when needed.

Any thoughts?

-AnandSomething similar to the concept of instantiation may be the Execute Package Task.
So considering a package as a logical unit like a container or a task, I imagine that an ipothetical "Execute Internal Task Task" (referred to a task in the control flow prepared once and reusable with different variables value etc..) could be a cool feature.
But I'm referring to Tasks in Control Flow, not to Data Flow trasformations (as you did in your post). A piece of a trasformation isn't a unit of your dts, only the whole Data Flow do is.
|||

Anand Desai wrote:

Hi,

Has anyone tried to explore the possibility of inheritence and instantiation within SSIS? For example, a derived column component being used in multiple data flow component or a same lookup component used multiple times in different data flow components.

Something very similiar to defining a class and instantiating it when needed.

Any thoughts?

-Anand

Yeah, loads of thoughts about it. The lack of reusability, the like of which you're talking about here, is one of main whinges about SSIS (as anyone that reads my blog will tell you).

As Umberto says, the only real way of doing this currently is to siphon functionality off into another package but even when doing this you're only talking about reusing tasks, not components which is what you want to do.

So yeah, lots of things that CAN be done, I've no doubt we'll see great strides made in this area in v2.

-Jamie|||Thanks for your thoughts!!
Using "Execute Package Task" will provide control flow synchronization. However, it doesn't not provide reusable components. At this point, making a single change in the data model trickles through all of my packages and it is quite cumbersome to copy, cut & paste. Also, copy/cut/paste is sometimes corrupting DTSX xml configuration by making lineage ids out of synch. The only way to resolve it is deleting the component and re-adding it.

I hope that we see some major improvements in v2.0 wrt reusability.

-Anand