70-467 · Question #132
You are designing a SQL Server 2012 Integration Services (SSIS) deployment strategy. You currently have many SQL Server 2008 SSIS packages that require upgrading. The production environment includes S
The correct answer is C. Use a package deployment model.. The package deployment model requires the least effort because it maintains full backward compatibility with SQL Server 2008 packages and preserves existing dtutil-based command shell scripts without modification.
Question
You are designing a SQL Server 2012 Integration Services (SSIS) deployment strategy. You currently have many SQL Server 2008 SSIS packages that require upgrading. The production environment includes SSIS 2012 and SSIS 2008. The environment includes existing command shell scripts that invoke the dtutil command-line utility. You need to design a deployment strategy that supports existing deployment strategies and requires the minimum amount of effort. 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
(37 responses)- A5% (2)
- B3% (1)
- C78% (29)
- D14% (5)
Why each option
The package deployment model requires the least effort because it maintains full backward compatibility with SQL Server 2008 packages and preserves existing dtutil-based command shell scripts without modification.
The project deployment model requires converting packages into an .ispac project file and deploying to the SSIS Catalog (SSISDB), which is incompatible with dtutil-based scripts and demands significant rework of both packages and deployment automation.
This choice is a duplicate of C and describes the same package deployment model - the question contains repeated answer choices, but C is designated as the best answer among the identical options.
The package deployment model deploys individual .dtsx files to the file system, MSDB, or a package store and is natively supported by the dtutil command-line utility referenced in the existing shell scripts. Because it is compatible with both SSIS 2008 and SSIS 2012, no package upgrades or script rewrites are required, satisfying the minimum-effort requirement while keeping the current deployment infrastructure intact.
The project deployment model requires migration to the SSIS 2012 Catalog and .ispac format, which breaks compatibility with existing dtutil shell scripts and increases migration complexity rather than minimizing effort.
Concept tested: SSIS package versus project deployment model selection
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.