Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

First Time Migration of a File System 2008 SSIS package from Dev to Prod Expand / Collapse
Author
Message
Posted Friday, September 7, 2012 11:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, September 10, 2012 10:40 AM
Points: 9, Visits: 33
Hi All,
I developed SSIS packages in our development server. I used my windows id in the development. The packages are created in the default location (My Windows id\documents\visual stiudio 2008\projects\...)

Now I want to move the development packages to production server. This is the first time so there are no packages in Prod SSIS. I cannot use my windows id in production server. The IT team has created a different windows id in the prod environment.

I am searching for migration procedures but couldnt understand a better way to do this.

The locations in my connection managers may change since the dev and prod doesnt have the same drives/folders etc.
I will modify the locations manually if I can move the packages first.

This might be a newbie question but Please give me suggestions on how to handle this. Thanks for your time and appreciate your help.




Post #1356145
Posted Wednesday, September 12, 2012 1:35 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, January 13, 2014 7:34 AM
Points: 117, Visits: 499
To do this we set-up a configuration file (Go SSIS-->Package configuration-->Add) where the location of the configuration file is stored as an environment variable

This way we only have to copy the packages from dev to prod and it automatically picks up the config file and adjusts the variables (my database connections use variables)

A good artice from Vyas Kondreddi on the subject:
http://vyaskn.tripod.com/sql_server_2005_making_ssis_packages_portable.htm

Mack
Post #1357818
Posted Thursday, September 13, 2012 2:59 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Friday, December 5, 2014 1:56 PM
Points: 1,587, Visits: 491
Using SSIS Variables for:
Data Locations - Process and Archive folders

Server Connections (Dev/Prod) - This is kinda cool, create connection strings using the variables, then when migrating just change the variable(s) (usually the Servername property in the expression for the connection)

After all the SSIS packages are tested and pass QA. We fill out deployment documents and have code reviews. The developer who wrote the package usually never deploys the code.

Last but not least is Stabilization...After the code has been deployed, the developer verifies all the processes are running correctly for the first few runs.

We also schedule jobs using proxy accounts.

If you are working on high visibility projects it is a good idea to come up with standard processes and to follow those processes. Most mistakes occur when code changes are done on the fly and under stressful circumstances.

Good Luck...


Post #1358900
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse