Start Ssis package variables not updating

Ssis package variables not updating

I have not had any compelling reason not to do it this way, although I’m sure there are cases where you may want them scoped differently.

While not a requirement to store the SQL Server package configuration in its own database, it is usually a good idea to do so.

Repeat steps 4 and 5 to add another Connection Manager; point to the Adventure Works database (or the database of your choice); we will use SQL Server Package Configuration to assign the Connection String property of this database.12.

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.

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.