Hi
I'm trying to add some parameters to the environment variables, so that they
can be specified in the jobs, is there any best practice to say that these kind of better to added in the environment variables.
thanks
MJ
Parameters in environment variables
Moderators: chulett, rschirm, roy
-
Maximus_Jack
- Premium Member
- Posts: 139
- Joined: Fri Apr 11, 2008 1:02 pm
I'm not terrible clear on what you're trying to ask. Here are some guidelines about variables:
Environment Variables - Only things pertaining to your server environment, nothing job specific should be at this layer. For example your SMTP server for the email stage because that's not likely to change from job to job. You'll hardly ever add/change these once you're setup and going.
Parameter Sets - Shared parameters for a single ETL job (The final scheduled sequence that starts your ETL). Leverage this for your Dev/Test/Prod settings in the values tab. Makes password changes or passing the same set of variables around very easy.
Job Parameters - Only variables specific to the individual job isolated from it's friends that comprise the whole ETL. You only need to parametrized what could change from run-to-run such as a file name or something.
Environment Variables - Only things pertaining to your server environment, nothing job specific should be at this layer. For example your SMTP server for the email stage because that's not likely to change from job to job. You'll hardly ever add/change these once you're setup and going.
Parameter Sets - Shared parameters for a single ETL job (The final scheduled sequence that starts your ETL). Leverage this for your Dev/Test/Prod settings in the values tab. Makes password changes or passing the same set of variables around very easy.
Job Parameters - Only variables specific to the individual job isolated from it's friends that comprise the whole ETL. You only need to parametrized what could change from run-to-run such as a file name or something.