Environment variables set up

Question

Environment variables set up

komal145

SSCrazy Eights

Points: 9915
More actions
October 11, 2016 at 2:54 pm

#322010

I have created a project parameters at my solution level and after i deploy the solution to the server ,at Integration Service catalog level i have to configure my parameters to point to environment variable every time when I deploy that package.
Is this can be avoided ( to configure the parameters to environment variables) every time ? do i need to change something at solution level? Please guide.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246686 More actions · Answer 1

komal145 (10/11/2016)
I have created a project parameters at my solution level and after i deploy the solution to the server ,at Integration Service catalog level i have to configure my parameters to point to environment variable every time when I deploy that package.
Is this can be avoided ( to configure the parameters to environment variables) every time ? do i need to change something at solution level? Please guide.

If you do the deployment from SSMS (right click/Deploy Project from within Integration Services Catalog), the mappings are retained.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

komal145 SSCrazy Eights Points: 9915 More actions · Answer 2

I think to be more specific, i am deploying the solution from visual studio. the other solution has no issues. only the solution which I am working has this.

Why do you deploy from SSMS to integration catalog. I did not get it?

Phil Parkin SSC Guru Points: 246686 More actions · Answer 3

komal145 (10/11/2016)
I think to be more specific, i am deploying the solution from visual studio. the other solution has no issues. only the solution which I am working has this.
Why do you deploy from SSMS to integration catalog. I did not get it?

Why? To avoid deployment issues. I never deploy SSIS projects from VS.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Jeff Moden SSC Guru Points: 1003851 More actions · Answer 4

Phil Parkin (10/11/2016)
komal145 (10/11/2016)
I think to be more specific, i am deploying the solution from visual studio. the other solution has no issues. only the solution which I am working has this.
Why do you deploy from SSMS to integration catalog. I did not get it?
Why? To avoid deployment issues. I never deploy SSIS projects from VS.

I've an even better solution. I never deploy SSIS projects... period. 😀

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Jack Corbett SSC Guru Points: 184393 More actions · Answer 5

Do you mean when you deploy to a new server or when you re-deploy to the same server because you made changes?

I have never seen this behavior and I deploy to dev and qa from VS all the time. I also just tried to duplicate it this behavior and I can't.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Phil Parkin SSC Guru Points: 246686 More actions · Answer 6

Jack Corbett (10/12/2016)
Do you mean when you deploy to a new server or when you re-deploy to the same server because you made changes?
I have never seen this behavior and I deploy to dev and qa from VS all the time. I also just tried to duplicate it this behavior and I can't.

Hmm, I've just tried in 2016 and can't replicate it either. However, I do remember deployments from VS causing major problems back in 2012, and it was related to project or package parameters getting values from the solution rather than as configured, from SSISDB. But I cannot remember any more specifically than that. I just know that ever since we had a meltdown, I've never tried again. I now use PoSh for automated deployments and SSMS for manual ones.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

MMartin1 One Orange Chip Points: 27764 More actions · Answer 7

I know there is a deployment utility within VS, though I've not used it much at all. Right click the name of the project in solution explorer > properties > configuration properties > deployment. Is this what you were using ?

----------------------------------------------------

komal145 SSCrazy Eights Points: 9915 More actions · Answer 8

Yes..i am deploying from Visual studio 2013. I chnaged property from " encrpyt sensitive data with USer key " to "Dont save sensitive data"....and deployed , i thought that fixed in production but again when we added something in dev( properties are same as prod , as we merged prod branch to Dev branch) and deployed to UAT...same issue.