You are deploying a new SQL Server Integration Services (SSIS) package to several
servers.
The package must meet the following requirements:
.NET Common Language Runtime (CLR) integration in SQL Server must not be enabled.
The Connection Managers used in the package must be configurable without editing the
package.
The deployment procedure must be automated as much as possible.
You need to set up a deployment strategy that meets the requirements.
What should you do?
A.
Use the gacutil command.
B.
Use the dtutil /copy command.
C.
Use the Project Deployment Wizard.
D.
Create an OnError event handler.
E.
Create a reusable custom logging component.
F.
Run the package by using the dtexec /rep /conn command.
G.
Run the package by using the dtexec /dumperror /conn command.
H.
Run the package by using the dtexecui.exe utility and the SQL Log provider.
I.
Add a data tap on the output of a component in the package data flow.
J.
Deploy the package by using an msi file.
K.
Deploy the package to the Integration Services catalog by using dtutil and use SQL
Server to store the configuration.
Reference:
https://msdn.microsoft.com/en-us/library/ms162820%28v=sql.110%29.aspx
0
0
I think K is closer to the answer.
0
0
.NET Common Language Runtime (CLR) integration in SQL Server must not be enabled.
So it cannot be deployed to catalog as catalog needs to have CLR enabled.
0
0
I don’t understand how:
The Connection Managers used in the package must be configurable without editing the
package.
informs the answer. When is a connection manager not editable without the package. Just parameterize the connection string. What else is there?
0
0
I think you might use a XML file to do this. ( which involves more work )
0
0
Also, the integrations services catalog needs clr. You need the dtutil to copy it into the msdb, dts or file
0
0