Wednesday, March 21, 2012

Moving SSIS packages from one machine to the other

I have developed some packages in my desktop, which works fine. I tried to move the project from my desktop to laptop by just copying the whole project folder. When I open the package within the project, it used to validate each package and used to hang for a longtime (Due to connection string etc). As Jamie suggested DelayValidation = TRUE sorted that problem out, which means the package opens now without hanging.

I still have problems with the migrated package. It lost the layout of my package. Also it lost the link between components. In other words I have got components scattered around without any green / red / blue lines between them.

I am sure it cant be as painful this is to migrate a package from one machine to the other. I am sure I am doing something wrong!! Please help!

Thanks
SuthaYou are correct, this is not expected to happen. It is hard to say what's wrong though, I don't remember seeing this problem.

Which version of SSIS do you have on these machines? Is it the same version on both machines?

Do you use any custom task in the package? If yes, is the task installed on both machines?

Does it happen with many packages or a single one? Were some errors reported to the error list, or did you get any error message box?|||I got June CTP on both machine. Yes I am using Trash component, but it is installed on both machines.

I am concentrating on a one package at the moment, loading customer dimensions package.

There are no error messages.

Thanks
Sutha|||Could you please send me the package?

michen (at) microsoft-dot-com

Thanks,
Michael.|||Michael

I have sent it to you. Thanks for your help.

Thanks
Sutha

No comments:

Post a Comment