Hi,
I'd like to manage some SSIS projects with a little administrative effort for SSIS developers and a separate management between prod and dev environments.
In order to do a such task, I think to use a set of project parameters to associate as properties for the connection managers used in a SSIS project.
To test the use of a project parameter:
a. I've created a project parameter to specify a SQL Server connection string;
b. I've associated this parameter to the connection string of the desired connection manager;
c. I've deployed the SSIS project on the SSIS catalog;
d. I've created a PROD environment for the SSIS project deployed on the SSIS catalog;
e. I've created for this PROD environment the related variables with the same names and values of the project parameters created and used in the SSIS project deployed;
f. selecting the project deployed in the SSIS catalog, for a specific parameter I've choosen the Use environment variable assigning the corresponding environment variable above created;
g. I've checked the Environment option and specified the PROD environment for the specific job step in order to use the project parameter.
The value of the environment variable about the connection string doesn't override the value of the project parameter created inside the SSDT: I'd like to manage once time for the prod environment the connection string for the connection managers letting free the SSIS developers to specify the values for the project parameters.
Any helps to me in order to define the right best practices to use project parameters in prod and dev environments?
Many thanks