70-463 · Question #139
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 Project Deployment Model (introduced in SQL Server 2012 SSIS) satisfies all four requirements. It stores packages in the SSISDB catalog and uses project-level parameters, allowing connection strings to be overridden at execution time without modifying packages. It natively…
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:
- Ensure that the deployment model supports changing the content of
connection strings by using parameters at execution time.
- Ensure that the deployment model automatically starts from calls to
the catalog.start_execution stored procedure in the SSISDB database.
- Maximize performance at execution time.
- Minimize development effort.
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 project deployment model.
- CUse a package deployment model.
- DUse a package deployment model.
How the community answered
(22 responses)- A73% (16)
- B5% (1)
- C18% (4)
- D5% (1)
Explanation
The Project Deployment Model (introduced in SQL Server 2012 SSIS) satisfies all four requirements. It stores packages in the SSISDB catalog and uses project-level parameters, allowing connection strings to be overridden at execution time without modifying packages. It natively supports execution via the catalog.start_execution stored procedure. It maximizes performance by keeping packages in memory within the catalog server. It minimizes development effort because connection managers and variables can be defined once at the project level and shared across all packages, rather than duplicating them per package. The Package Deployment Model relies on XML config files or environment variables and does not integrate with the SSISDB catalog or catalog.start_execution. Note: answer choices A and B are textually identical in this question; both represent 'project deployment model.'
Topics
Community Discussion
No community discussion yet for this question.