A somewhat odd question about parameters and environments
Posted: Thu Jun 02, 2005 8:12 am
I'm implementing a number of jobs on a pretty 'standard' working environment. I.e there's a development server, a test server and a production server (well, the production server's not there yet but it will be in a while).
Jobs are moved between the servers using Version Control, in a standardized way.
In order to allow for different connect strings to databases I've implemented them as parameters using Project Environment Variables in the job sequences that I use to call the actual jobs doing the data shuffling. I.e the job sequences have Environment Variables defined, using the $PROJDEF option to always read the current value in the repository, and use these values as in-parameters to the server jobs.
This means that all that needs to be done when moving a job from Dev to Test or Prod is to set up the proper Project Variables on Test or Prod and set whatever values needed, and then all jobs will get the right values as needed.
I can't see that there could be a more practical way to solve this, and does anyone disagree with me in that this would be the 'best practice' way of doing things?
The reason I ask is that I've had requirements laid on me for another solution that I would not recommend to implement and I'd like to know that what I'm recommending is the standard and most practical solution.
Jobs are moved between the servers using Version Control, in a standardized way.
In order to allow for different connect strings to databases I've implemented them as parameters using Project Environment Variables in the job sequences that I use to call the actual jobs doing the data shuffling. I.e the job sequences have Environment Variables defined, using the $PROJDEF option to always read the current value in the repository, and use these values as in-parameters to the server jobs.
This means that all that needs to be done when moving a job from Dev to Test or Prod is to set up the proper Project Variables on Test or Prod and set whatever values needed, and then all jobs will get the right values as needed.
I can't see that there could be a more practical way to solve this, and does anyone disagree with me in that this would be the 'best practice' way of doing things?
The reason I ask is that I've had requirements laid on me for another solution that I would not recommend to implement and I'd like to know that what I'm recommending is the standard and most practical solution.