SSIS Linux: Are environment variables supported for configuration? RRS feed

  • Question

  • We're trying to use an environment variable to configure an SSIS package run on Linux using dtexec. The environment variable works on Windows, but does not seem to work on Linux:

    Description: The configuration environment variable was not found.  The environment variable was: "ENVIRONMENT". This occurs when a package specifies an environment variable for a configuration setting but it cannot be found. Check the configurations collection in the package and verify that the specified environment
    variable is available and valid.

    I've tried both:

    env ENVIRONMENT=dev /opt/ssis/bin/dtexec /F <package>

    export ENVIRONMENT=dev
    /opt/ssis/bin/dtexec /F <package>

    The package contains:

          DTS:ObjectName="Environment" />
    Are environment variables supported?


    • Edited by AndrewDMay Monday, September 9, 2019 12:44 PM
    Monday, September 9, 2019 12:40 PM

All replies

  • Hi Andrew,

    This is somewhat old approach back to the more than a decade old SSIS 2005 - 2008R2 era.

    Starting from SSIS 2012 onwards, SSISDB Catalog is a preferred method. It has quite a few ways to control environment dependencies:

    • Project parameters.
    • Package parameters.
    • SSIS Environments.
    • Project connection managers.
    Monday, September 9, 2019 1:16 PM
  • Hi Yitzhak,

    We're not using SQL Server (and I'm not sure the SSISDB Catalog is supported with Linux - see and are just executing dtexec directly, so that limits us to package based configurations.

    Environment variables were more convenient than dtsConfig files and work on Windows but don't appear to work on Linux, but I'm asking to get a definitive answer.


    Monday, September 9, 2019 1:44 PM
  • Hi AndrewDMay,

    Please refer to the following links.

    Configure SQL Server settings with environment variables on Linux

    Limitations and known issues for SSIS on Linux

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Tuesday, September 10, 2019 7:19 AM