Guitar_player (12/17/2014)
Hi , I should not use ?I have tried the other method as Deployed my project in the SSIS catalog and then created a Environment variable in the SSIS catalog and assigned to a project parameter and this is done through my local server and i am running the Master package by creating the job
But my requirement is something like on whatever server i am deploying i will configure the windows environment variable and the Master package should consider the Environment variable Server Name in that server and i just i need to execute the Job and not doing anything manually and it should be automatic on any server that i deploy for ..
So i hope i was able to convey what i require ...if this can be done easily by the way your suggesting ..pls let me know the process and how it can be accomplished easily on other servers too..
Thanks & Regards,
Guitar_Player
In 2012, I see no need to use Windows EVs (WEVs) any more.
You mention that you want to be able to deploy the project, configure one WEV and then be able to run it, without 'doing anything manually'.
But in your original post, you also state that:
We have defined the Warehouse and Oracle Connection strings in SQL server Table of the Staging DB .
So there's clearly more to this task than you suggest, because the staging DB needs to be updated too.
Instead, you have the option of
1) Default all of your parameters and connections to dev values, so that you can always open them in SSDT.
2) After deploying to a non-dev server, create a SQL Agent job to run the package.
a) In your agent job, you can override any of the parameters and connections directly.
b) Or your can create an SSIS Environment (in the SSIS catalog) to contain all of the connections and parameters and associate that with the project.
Unlike a WEV, this makes the process more transparent.
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.