Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm re-designing some SSIS packages for 2012 and some parameter/variable/configuration issues are not clear to me.

The result that I am trying to achieve is that the user context's temp folder(stored in the %temp% OS environment variable) is available in my package. Specifically, when I open the package in SSDT, it should expand the environment variable to the current path so that it passes validation. I can get this at run time with script task, but it's ugly working around it at design time. In the SSIS catalog, I can apply an environment variable to a parameter, so that aspect is not an issue.

How can I get this to happen when a project is opened?

share|improve this question
Your need is that during design time, you want a variable/parameter to point to a location determined by an OS variable and during run time from the SSISDB catalog, it you'll have that parameter configured from an SSIS Environment variable? – billinkc Jun 11 '13 at 15:26
I believe so. The connection manager fields have expressions that include variables. Those variables come from parameters. In the catalog, parameters can be provided from environment variables. In SSDT, they can come from configurations. I am try to learn if external data can be included in configurations and when that inclusion happens. – Jeff Sacksteder Jun 11 '13 at 16:18
Jeff, in order for a commentator to know that you replied you must use @ and his name in your reply, like @billinkc in this case. – Roi Gavish Jun 16 '13 at 16:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.