July 28, 2003 at 5:25 pm
I'm trying to reduce the amount of hardcoding in our product, which uses about 230 DTS packages to control the ETL process. What I really need is the method for passing global variable values from a child package back to the parent DTS package. Without this, I'm hosed and will have to return to hardcoding. Anybody have experience in this?
July 28, 2003 at 5:57 pm
The only way that I can think of to do this is to pass the values in a working table. To do this most certainly, I would probably generate a GUID in the parent table, set the values into a working table (call it PackageVars), pass the GUID to the child task, and update those values in an SQL task, using the GUID and a value name as the key.
Then, the Parent would update its own internal variables (if needed) from the table, and go to the next step. Repeat above as needed.
Batteries not included. Some assembly required.
quote:
I'm trying to reduce the amount of hardcoding in our product, which uses about 230 DTS packages to control the ETL process. What I really need is the method for passing global variable values from a child package back to the parent DTS package. Without this, I'm hosed and will have to return to hardcoding. Anybody have experience in this?
July 29, 2003 at 9:13 am
That is an ingenious and elegant solution. I was hoping that the global variable passing was not a one way street - from parent to child - but this solution will work for me. Thank you for your help. Hmmm.. how do we get Microsoft's DTS team to upgrade their functionality? It's obvious that the DTS package can see the global variables and their values in child packages, since they can be selected in the GUI (Inner Package Global Variables). It's a shame that this isn't incorporated in the workflow.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply