nerdexam
Microsoft

70-463 · Question #144

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 dat

The correct answer is B. For each target server, create separate Environments in the SSIS catalog of the host SQL. In the SSIS Project Deployment Model, Environments in the SSIS catalog are the native mechanism for supplying server-specific values at execution time. An Environment is a named container of variables, each of which can be mapped to a project parameter or connection string proper

Configure and deploy SSIS solutions

Question

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?

Options

  • AFor each target server, create separate registry entry configurations.
  • BFor each target server, create separate Environments in the SSIS catalog of the host SQL
  • CCreate one SSIS catalog Environment.
  • DFor each target server, create a separate XML configuration file.

How the community answered

(60 responses)
  • A
    3% (2)
  • B
    78% (47)
  • C
    13% (8)
  • D
    5% (3)

Explanation

In the SSIS Project Deployment Model, Environments in the SSIS catalog are the native mechanism for supplying server-specific values at execution time. An Environment is a named container of variables, each of which can be mapped to a project parameter or connection string property. By creating one Environment per target server - each holding that server's connection strings and parameter values - an administrator simply references the appropriate Environment when scheduling or executing the package. This is less effort than XML config files (which require file-system access and manual distribution) or registry entries (which require registry access on each server). Creating only one Environment (choice C) cannot support five different sets of values simultaneously.

Topics

#SSIS catalog environments#multi-server deployment#environment variables#Project Deployment Model

Community Discussion

No community discussion yet for this question.

Full 70-463 Practice