Hello,
I created a SSIS project with some SSIS packages within my local machine. Once all development and testing stuff was finished I imported the same to SSIS package store within Integration services. Then I created another test folder within my local machine and copied all the packages along with the project .sln file to that test folder.
Now the problem, If I make any changes to the package within test folder it automatically saves the changes to my other folder. Does anybody have a reason why it is doing so.
Thank You
Jatin
Making changes to SSIS packages
Andreas Pollak
Yes that would be my thought too.
While in the new/copied solution, click on each package name in the solution explorer and view the 'Full Path' property and verify they are what you think. Another place I have burned myself is copying a solution with parent packages calling children packages....and forgetting to update the connection manager used by the ExecutePackage task to point to the new child rather than the old child...mmm sounds a bit like a soap opera.
hope that helps.
pnp
Jamie,
Thank you, I got the problem.
Moshe Gutman
I'm guessing its because the solution still contains a reference to the original .dtsx file.
-Jamie