nerdexam
Microsoft

70-463 · Question #14

You are using SQL Server Data Tools to develop a SQL Server Integration Services (SSIS) project. The first package that you create in this project contains a package connection that accesses a flat fi

The correct answer is A. Convert the package Connection Manager in the first package to a project Connection. To share a connection across all packages in an SSIS project, you must promote it from a package-level Connection Manager to a project-level Connection Manager. Only the Project Deployment model supports project-level Connection Managers.

Configure and deploy SSIS solutions

Question

You are using SQL Server Data Tools to develop a SQL Server Integration Services (SSIS) project. The first package that you create in this project contains a package connection that accesses a flat file. Additional packages in the project must also access this file. You need to define and reuse the flat file connection in all project packages. What should you do?

Options

  • AConvert the package Connection Manager in the first package to a project Connection
  • BCopy the package Connection Manager and paste it into the second package.
  • CConvert the project to the Package Deployment model.
  • DSet the ProtectionLevel property of the package Connection Manager to DontSaveSensitive

How the community answered

(49 responses)
  • A
    90% (44)
  • B
    2% (1)
  • C
    6% (3)
  • D
    2% (1)

Why each option

To share a connection across all packages in an SSIS project, you must promote it from a package-level Connection Manager to a project-level Connection Manager. Only the Project Deployment model supports project-level Connection Managers.

AConvert the package Connection Manager in the first package to a project ConnectionCorrect

Converting a package Connection Manager to a project Connection Manager promotes it to the project scope, making it available to every package in that project without duplication - this is the purpose of project-level connections in the Project Deployment model in SQL Server Data Tools.

BCopy the package Connection Manager and paste it into the second package.

Copying and pasting a Connection Manager creates an independent duplicate in the second package; the two copies are not linked and must be maintained separately.

CConvert the project to the Package Deployment model.

Converting to the Package Deployment model removes project-level features including project Connection Managers, making it impossible to share connections across packages.

DSet the ProtectionLevel property of the package Connection Manager to DontSaveSensitive

The ProtectionLevel property controls how sensitive data such as passwords is stored in the package, and has no effect on whether a connection is scoped to a package or shared across the project.

Concept tested: SSIS project-level Connection Manager promotion and reuse

Source: https://learn.microsoft.com/en-us/sql/integration-services/connection-manager/integration-services-ssis-connections

Topics

#project Connection Manager#package Connection Manager#SSIS project#flat file connection

Community Discussion

No community discussion yet for this question.

Full 70-463 Practice