Link to home
Start Free TrialLog in
Avatar of Tyecom
TyecomFlag for United States of America

asked on

SSIS Deployment

I created a SSIS solution that contains multiple packages.  Now I need to deploy the solution to another computer.  I've read an article regarding creating a "package configuration", but is very confused with what I'm reading.  I just want to deploy the solution to another computer and make sure it runs properly.  The package configuration file I created, includes the "connection managers, properties, and pretty much everythiing else.  Is this all necessary?  I'm I making this more difficult then it has to be?  Thanks in advance.
SOLUTION
Avatar of Jim Horn
Jim Horn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ggzfab
ggzfab

I'm using multiple environments (Development/Test/Production) on multiple servers to manage the packages in their lifecycle.
Thus I've created the same folder structure on all servers and made sure the packages have the Protection level in the Properties set to "DontSaveSensitive" and the Package configuration has been set to a XML configuration file that's pointed to by a System variable.

Now make sure that the System variable with the XML configuration file is set properly and that the XML configuration file contains the proper connections for the environment.
Moving a package can be done in this setting by a simple file move.
Avatar of Tyecom

ASKER

Is the basic advantage to creating a package configuration file is when you're using variables?  For a simple deployment, why not just copy the folder containing the project to the destination computer?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial