Variables Sharing Values Across Multiple Instances Of The SSIS Package?
I have a SSIS package that I execute from multiple Agent Jobs with different /CONNECTION parameter values. This means that they will connect to different data source. Sometimes when the jobs are running in parallel, I have seen a situation where the variable values get mixed up between different instances of the package. I tried to search a solution for this but so far haven't found anything. I have seen other references to this issue so it seems to be somehow possible. Is there something I could do to prevent this from happening?
November 22nd, 2012 6:30am

Pesonally i havent seen this sort of thing happening, a long shot though i think the variables are PACKAGE SCOPE you might want to change the scope to appropriate level as they are required then give it a try. Or reassing the varaibles somewhere before the probelemtic area where you see the problem happening on the package using a Script taskAbhinav http://bishtabhinav.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2012 6:44am

I'm not sure if it is the actual variable values that get mixed up between instances or the connection manager ConnectionString. What I'm seeing, is that one instance of the package tries to connect to the data source based on the other instances connection.
November 23rd, 2012 12:43am

It seems that the problem is not in some weird sharing of variable values but instead of just SSIS overriding the ConnectionString of my Connection Manager with the Design-Time values after I set the with run-time parameters. I've created a new thread about this issue. http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/35522bec-4b40-4188-bf46-1ccb875e7e71
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2012 7:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics