70-467 · Question #45
You are designing a SQL Server Integration Services (SSIS) solution. The solution will contain an SSIS project that includes several SSIS packages. Each SSIS package will define the same connection…
The correct answer is A. Use a project deployment model. The SSIS project deployment model supports project-level parameters for runtime connection string overrides and provides automatic event logging to the SSISDB catalog database.
Question
You are designing a SQL Server Integration Services (SSIS) solution. The solution will contain an SSIS project that includes several SSIS packages. Each SSIS package will define the same connection managers and variables. You have the following requirements:
- The deployment model must support changing the content of connection
strings by using parameters at execution time.
- The deployment model must automatic ally log events to the SSISOB
database.
- Maximize performance at execution time.
You need to design a solution that meets the requirements. What should you do? (More than one answer choice may achieve the goal. Select the BEST answer.)
Options
- AUse a project deployment model.
- BUse a package deployment model.
- CUse a package deployment model.
- DUse a project deployment model.
How the community answered
(18 responses)- A94% (17)
- D6% (1)
Why each option
The SSIS project deployment model supports project-level parameters for runtime connection string overrides and provides automatic event logging to the SSISDB catalog database.
The project deployment model deploys packages to the Integration Services catalog (SSISDB), which automatically captures events and operational data without requiring manual logging provider configuration. It also exposes project-level and package-level parameters that allow connection strings to be overridden at execution time, and catalog-based execution is optimized for server-side performance, satisfying all three requirements.
The package deployment model does not support automatic logging to the SSISDB catalog and requires manual logging provider setup, failing the automatic event logging requirement.
This choice is identical to option B - the package deployment model lacks native SSISDB integration for automatic logging and does not provide project-level parameter support for runtime connection string changes.
This choice is identical to option A and represents the same correct approach; it is a duplicate distractor in the question and does not represent a distinct alternative.
Concept tested: SSIS project deployment model vs package deployment model
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.