Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

Environment variable in SSIS not being recognized

If you are using environment variables in SSIS when using package configuration, chances are you will run into a situation where you add or change the value of an environment variable, and SSIS does not recognize it.  There is a misconception that in order for the packages to start recognizing it, the machine needs to be restarted.  The reality  is that just the process which is running the SSIS packages needs a restart. Typically this is the SQL agent if you have a job that is executing the package, or you will need to restart the SSIS service if you are running the package directly.  In a development environment, BIDS would need a restart.

In my SSIS packages I typically use package configurations, having an environment variable called SSIS_CONFIG_DB that defines the connection string to my SSISConfig database.  In this database is a table called SSISConnectionConfig, which contains the connection info for all the connections used in the package.  So, if I have SSIS_CONFIG_DB pointing to development and I’m in Visual Studio testing the package, if I then change SSIS_CONFIG_DB to point to production, I must exit Visual Studio and start it back up again for Visual Studio to start using production.


Posted by Anonymous on 12 July 2011

Pingback from  Dew Drop – July 12, 2011 | Alvin Ashcraft's Morning Dew

Leave a Comment

Please register or log in to leave a comment.