Using Metadata for child package columns, transforms etc

Jun 3, 2010 at 7:36 AM

This is a good framework , I would be interested to know your thoughts on using meta data to drive the child package , ie store all the columns / column names / transforms to use entirely within database tables. The set up of a new package would then involve nothing on the SSIS front but could be entirely configurable by T-SQL scripts.

I am giving some serious thought to doing this, has anyone seen it done before?

Coordinator
Jun 6, 2010 at 11:58 AM

Thanks - I hope to get it into beta soon, all development is done, it just needs testing properly.

Using MetaData to drive the child package is an interesting idea but would be difficult to do without using something like CozyRoc's Data Flow Plus, simply because SSIS works on the basis of fixed metadata. I can only see this working if you call an application that builds the package at runtime based on that metadata (which is possible).

One of the next steps for the framework will be an application that builds framework compliant packages based on input metadata, but that requires me to up my C# skills considerably first...