February 20, 2014 at 10:25 am
Hi all,
I've copied a package (so as to retain the connections/tasks), however when I try to create variables, their scope defaults to the previously copied package, no matter that I've closed the first package, and the dialogue box doesn't permit me to change.
Anyone know how to change scope, preferably without recreating the entire 2nd package from scratch?
Thanks
February 20, 2014 at 12:42 pm
I would recommend BIDS Helper for this task (and not only for this). It's a great extension for business intelligence development studio (BIDS). Here is the link https://bidshelper.codeplex.com/wikipage?title=Variables%20Window%20Extensions
___________________________
Do Not Optimize for Exceptions!
February 21, 2014 at 3:27 am
That did not work, I installed the program but the Move/Copy function doesn't even show other packages, the only option is to change the scope within the same package elements (WTF??) which makes it useless.
Anything workaround? I've tried rebuilding the target package, but again, no luck.
February 21, 2014 at 4:35 am
So you want to change the scope of a variable from one package to an entirely different package; is that correct? If so, I don't think this can be done as , prior to SSIS 2012, the highest level at which a variable can be scoped is the package level. the scope can be changed to different tasks within a single package, but not to a different package AFAIK.
Regards
Lempster
February 21, 2014 at 7:11 am
I have not run into this issue, but just in case. In the properties for the package, change the name of the package a little, and generate a new GUID, then save it, close it, and reopen it. Then try your variable scoping again.
February 21, 2014 at 7:22 am
Lempster (2/21/2014)
So you want to change the scope of a variable from one package to an entirely different package; is that correct? If so, I don't think this can be done as , prior to SSIS 2012, the highest level at which a variable can be scoped is the package level. the scope can be changed to different tasks within a single package, but not to a different package AFAIK.Regards
Lempster
Just to add to what I posted earlier, it is possible to pass variables from a Parent package to a Child package of course.
December 31, 2014 at 1:41 pm
I just came across this same issue. How the issue was created was that I copied an SSIS package and renamed it BEFORE bringing it into BIDS. Doing that I was not able to change the scope of the existing variables to reflect the new name of the SSIS package.
After reading this thread I decided to bring in the copied package (with no name change) into BIDS. I then renamed the package within BIDS. After doing so the scope now picked up the newly named package. In the properties window it was immediate but I needed to close the package and reopen for the scope of the variable to be reflected in the variable window.
Hope that helps.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply