You are developing a SQL Server Integration Services (SSIS) project by using the Project
Deployment Model.
The project is deployed to a single SSIS catalog, and transfers data to and from multiple
databases hosted on SQL Server.
The project must be configured to be able to export data to and from five different production
servers that run SQL Server 2012. Each target server requires different values for
connection strings and parameters in the SSIS project.
You need to meet the requirements by using the least amount of administrative effort.
What should you do?
A.
For each target server, create separate registry entry configurations. Select the registry
entry at package execution time.
B.
For each target server, create separate Environments in the SSIS catalog of the host SQL
Server SSIS instance. Select the appropriate Environment at package execution time.
C.
Create one SSIS catalog Environment. Change the values of each Environment variable
at package execution time.
D.
For each target server, create a separate XML configuration file. Select the XML
configuration file at package execution time.
Why not C? We need just one environment… different values for each target servers
Option C is quite vague. It doesn’t capture a feasible solution to the scenario as depicted. Option B is the only feasible solution.
Agree with Slazenjer. Option C is right.
…Each target server requires different values for connection strings and parameters
Sorry, I mean ‘option B’