September 16, 2009 at 3:20 pm
I am testing a package that runs 5 script tasks in parallel. Each script task has exactly the same code in it, but one of the input read-only variables is different for each one. So task1 gets Var1, task2 gets Var2 etc.
If I run the package with only 4 tasks - all is well. As soon as I go to 5, the 5th task reads its variable Var5 and finds it blank, even though I have confirmed earlier in the package that it is not blank. Other variables that are shared with all tasks have their proper values.
I have tried setting PrecompileScriptIntoBinaryCode false on each task and also tried setting OptimizeScriptExecution to false on each task. Nothing seems to work.
Any thoughts on what is wrong here? Is this a known bug in SSIS 2005?
I have run the package on my laptop thru Visual Studio 2005 (connecting to SQL Servers on other machines) and also run the package directly on one of the SQL Servers using SQL Agent. Same result. SQL Server 2005 is Service Pack2.
September 17, 2009 at 9:42 am
I found the problem - argggh - the "missing" variable from global scope was being hidden by a variable of the same name at a lower scope, accidentally created at that scope.
So SSIS works just fine with 5 parallel script tasks :ermm:
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply