70-463 · Question #61
You are developing a SQL Server Integration Services (SSIS) package that imports data into a data warehouse hosted on SQL Azure. The package uses a Foreach container to process text files found in a…
The correct answer is C. Environment Variable. In the Project Deployment model, SSIS environments and environment variables are the correct mechanism for supplying different runtime parameter values to packages called by separate SQL Server Agent jobs.
Question
You are developing a SQL Server Integration Services (SSIS) package that imports data into a data warehouse hosted on SQL Azure. The package uses a Foreach container to process text files found in a folder. The package must be deployed to a single server by using the Project Deployment model. Multiple SQL Server Agent jobs call the package. Each job is executed on a different schedule. Each job passes a different folder path to the package. You need to configure the package to accept the folder path from each job. Which package configuration should you use?
Options
- AParent Package Variable
- BXML Configuration File
- CEnvironment Variable
- D.dtsConfig file
- ERegistry Entry
How the community answered
(48 responses)- A2% (1)
- B2% (1)
- C81% (39)
- D10% (5)
- E4% (2)
Why each option
In the Project Deployment model, SSIS environments and environment variables are the correct mechanism for supplying different runtime parameter values to packages called by separate SQL Server Agent jobs.
Parent Package Variable is used to pass values from a parent SSIS package to a child package during package-to-package execution, not from SQL Server Agent jobs.
XML Configuration Files are a legacy Package Deployment model feature and are not used or recognized by the Project Deployment model.
The Project Deployment model stores packages in the SSISDB catalog and uses SSIS environments to supply parameter values at execution time. Each SQL Server Agent job can reference a different environment that defines a distinct folder path value, so each job passes its own path to the package without any package modification.
.dtsConfig files are part of the legacy Package Deployment model and are incompatible with the Project Deployment model.
Registry Entry configuration is a legacy Package Deployment model option and is not available when using the Project Deployment model.
Concept tested: SSIS Project Deployment model environment variable for runtime configuration
Source: https://learn.microsoft.com/en-us/sql/integration-services/packages/deploy-integration-services-ssis-projects-and-packages
Topics
Community Discussion
No community discussion yet for this question.