I have to deploy a set of packages from the development server to the test server and later on to the production server.
Due to new security policy, developers have no access to the production server, so I have to prepare a deployment strategy.
I used package configuration, and it is stored in the SQL Server (DEV Server).
In the past I got into the production server, open the package and set the connection to the right SSIS configuration Table manually.
I also used other option, is to create the configuration table where the packages are going to be executed, then the address or server name of the configuration table is "." or "(local)"
In this way it didn't need to adjust the connection to the server if a move the configuration table, if and only if the packages are stored and are executed in the same server and this server is the default server.
I dislike both methods because they are not general and work only under specific conditions.
I read something about environment variables but it doesn't convince me.
Any other suggestion will be appreciated.