How to change XML config file path in SSIS during deployments

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

Hi All,

After a long google search I came here for clarifications.

I am new to SSIS.But am aware of few tasks .Recently I got a requiremnt for an SSIS job.I have developed and working fine in dev .Now its time for QA deployment

Now questions started

In my dev environment ,I have created one XML config file which is there in my C drive.So every time I run the package,values taking from this config file.

Now I want to deploy this package in QA environment.But my package config file is pointing to my machine C drive . How to change this path to QA path (another path).
Is there any process to do this externally ?

I read env variables is one option .But my DBAs are not accepting by this way.

How I do in Production deployment?

Please suggest.

Thanks in advance.

Posted 7-Jan-15 8:35am

Member 11283674

Add a Solution

Comments

PIEBALDconsult 7-Jan-15 14:41pm

I've been doing SSIS almost exclusively for the last three years.
If at all possible, upgrade to 2012, there are a great many improvements to SSIS.
I recommend using project parameters for paths and such.

Also, if by "env variables" you mean operating systems-level variables, don't use those. But SSIS (at least in 2012) has its own environment variables and they're awesome!

Member 11283674 8-Jan-15 12:04pm

we were planned to go for 2014 ,but it will take time.Present we are stick with 2008r2.
is there any other way to do this?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)