Make 1 Variable accessable by 3 Packages
Hi Experts,
Firstly I have to ask is this even possible.
I have 3 SSIS Packages in one Solution (I'm not sure of the proper name in BIDS) and each of them use the same server and the same DB.
Each Package needs its own Connection and I have put the Server name in the connection as a variable (Thinking it would save a lot of time, but I was wrong) I still have to change the variable value for each Package.
Is there a way I can connect the variable up to look at a global value so all 3 package connections get updated. The reason I do this is when in Development I hit the Dev servers and then I can change to value for production to hit the production servers.
Thanks in advance and I hope the question is not totally off the wall
Firstly I have to ask is this even possible.
I have 3 SSIS Packages in one Solution (I'm not sure of the proper name in BIDS) and each of them use the same server and the same DB.
Each Package needs its own Connection and I have put the Server name in the connection as a variable (Thinking it would save a lot of time, but I was wrong) I still have to change the variable value for each Package.
Is there a way I can connect the variable up to look at a global value so all 3 package connections get updated. The reason I do this is when in Development I hit the Dev servers and then I can change to value for production to hit the production servers.
Thanks in advance and I hope the question is not totally off the wall
ASKER
Jim,
Thanks for your response and I tried to use the deployment manager already but not for this and as my Dev server is only 2008 it just stayed greyed out, so I changed the server to a 2012 server just to see what would happen and it became active but then complained that it couldn't find the (SSISDB).
The second option is possible and I will talk to the other guys about it and see how they feel, but it is definitely an option.
Thanks
Thanks for your response and I tried to use the deployment manager already but not for this and as my Dev server is only 2008 it just stayed greyed out, so I changed the server to a 2012 server just to see what would happen and it became active but then complained that it couldn't find the (SSISDB).
The second option is possible and I will talk to the other guys about it and see how they feel, but it is definitely an option.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@nishant,
The configuration file I would be very interested in and I will search my knowledge base (Google) for more info, but if you know of any good sites with more info on both SSIS 2012 and SSIS 2008 it would be greatly appreciated.
Thanks
The configuration file I would be very interested in and I will search my knowledge base (Google) for more info, but if you know of any good sites with more info on both SSIS 2012 and SSIS 2008 it would be greatly appreciated.
Thanks
Niall292, do you still need help with this question?
ASKER
I have not tried it yet because I was put on another project but it seems the most plausable
I've also seen a lot of places where SSIS connection info is stored in a table, often encrypted, and SSIS packages make a call to that table to get connection info, assign the values to variable(s), then the connections are driven by those variable(s).
Good luck.
Jim