Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


How to Use XML Config File to Allow SSIS Pkg to Run Successfully on Development/Production...


How to Use XML Config File to Allow SSIS Pkg to Run Successfully on Development/Production Locations?

Author
Message
brad.mccollum
brad.mccollum
Valued Member
Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)

Group: General Forum Members
Points: 73 Visits: 329
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.
Eirikur Eiriksson
Eirikur Eiriksson
SSCertifiable
SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)SSCertifiable (6.8K reputation)

Group: General Forum Members
Points: 6766 Visits: 17739
The most usual approach is to use one file for each environment, a dev config, a testing config and a production config.
Cool
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search