Jamie (I couldn't respond over on the MSDN forum because of the bug in hotmail/passport leading to redirection failure, too many url redirections on Microsoft's servers),
This looks very promising.
However, I would not look forward to the copy&paste nightmare of copying and pasting this exact INSERT statement across every DTS package in every DTS solution -- the usual problem of widespread copy&paste, that it would discourage making any subsequent changes to it, because of the cost of changing all the copies, especially slowly in the Visual Studio editor.
I'm thinking that some of that problem could be alleviated by encapsulating the statement into a UDF (SQL Server user defined function). The variable access couldn't be so encapsulated unfortunately, but at least the INSERT statement could.
This really goes back to what I assume is still an outstanding problem in SQL Server 2005 SSIS, which is code reuse in expressions -- I don't know any solution for that -- that is, to be able to encapsulate expressions for reuse. I've not yet tried the June CTP though.
This looks very promising.
However, I would not look forward to the copy&paste nightmare of copying and pasting this exact INSERT statement across every DTS package in every DTS solution -- the usual problem of widespread copy&paste, that it would discourage making any subsequent changes to it, because of the cost of changing all the copies, especially slowly in the Visual Studio editor.
I'm thinking that some of that problem could be alleviated by encapsulating the statement into a UDF (SQL Server user defined function). The variable access couldn't be so encapsulated unfortunately, but at least the INSERT statement could.
This really goes back to what I assume is still an outstanding problem in SQL Server 2005 SSIS, which is code reuse in expressions -- I don't know any solution for that -- that is, to be able to encapsulate expressions for reuse. I've not yet tried the June CTP though.