SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 

Phantom SSIS Changes

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.


Filed under: Microsoft SQL Server, SQLServerPedia Syndication, SSIS Tagged: microsoft sql server, SSIS

SQLStudies

My name is Kenneth Fisher and I am Senior DBA for a large (multi-national) insurance company. I have been working with databases for over 20 years starting with Clarion and Foxpro. I’ve been working with SQL Server for 12 years but have only really started “studying” the subject for the last 3. I don’t have any real "specialities" but I enjoy trouble shooting and teaching. Thus far I’ve earned by MCITP Database Administrator 2008, MCTS Database Administrator 2005, and MCTS Database Developer 2008. I’m currently studying for my MCITP Database Developer 2008 and should start in on the 2012 exams next year. My blog is at www.sqlstudies.com.

Comments

Leave a comment on the original post [sqlstudies.com, opens in a new window]

Loading comments...