Phantom SSIS Changes

Leave a comment

July 5, 2016 by Kenneth Fisher

That SSIS change just won’t stick! There is a new business requirement, so now you have to change an existing SSIS package. You opened up a new project, imported the package, and made your changes.

Adding the original package to the new project.

Adding the original package to the new project.

Make changes to the old package in the new project.

Changes made to the old package in the new project.

But the changes just aren’t showing up. You back and look again and sure enough, the changes you made are there. You run your job (or whatever) and still the change aren’t taking effect. So what happened?

When you add an existing package to a project it makes a copy of the package.

The old package, in the old project.

The old package, in the old project.

Old package location in the new project.

Old package location in the new project.

In order for the changes to take effect you need to move the .dtsx file (the package) back to the original location. The easiest way I’ve found to do this is just a simple file copy.

Obviously this is only an issue with Package Deployment not Project Deployment but you would be amazed how often this has come up.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 2,148 other followers

Follow me on Twitter

ToadWorld Pro of the Month November 2013
%d bloggers like this: