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

How to Use XML Config File to Allow SSIS Pkg to Run Successfully on Development/Production Locations? Expand / Collapse
Author
Message
Posted Monday, April 14, 2014 2:16 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Saturday, July 5, 2014 8:31 AM
Points: 31, Visits: 220
I'm new to SSIS and am working my way through a project for a client in order to get some valid SSIS experience under my belt.

I will hopefully finish the project in about a month and am curious as to how to configure/use an XML config. file to allow the project to run successfully in my development environment, but also run successfully in the client's production environment once it's installed there.

I believe that most of the XML config. file will need to contain unique entries for several variables that will need to be set to specific values to allow the package to run in both environments, but I'm not quite sure as to the specifics as to how to do that.

For example, let's say I've got a variable named "sExcelFileRoot" and it's set for "c:\IncomingExcelFiles\" in the development environment. The proper setting for "sExcelFileRoot" may need to be "c:\SSISProject\IncomingFiles\" in the production environment. Similar situation exists for numerous variables that will need to be set to one entry to work appropriate in the development environment, and set to different entries to seamlessly allow the SSIS to function properly in the production environment.

Do I need 2 XML config. files, one that's utilized to dynamically set the variables in the development environment and another one that will reside in the production environment and has the variables set appropriately to permit successful SSIS package execution in that environment?

Any assistance w/my questions is greatly appreciated.
Post #1561668
Posted Monday, April 14, 2014 4:35 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 9:24 AM
Points: 1,270, Visits: 3,657
The most usual approach is to use one file for each environment, a dev config, a testing config and a production config.
Post #1561688
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse