You are troubleshooting an existing SQL Server Integration Services (SSIS) package. On
several occasions, the package execution does not finish and no data seems to have been
transferred.
You need to ensure that package logging occurs. Your solution must minimize deployment
and development efforts.
What should you do?
A.
Run the dtutil command to deploy the package to the SSIS catalog and store the
configuration in SQL Server.
B.
Use an msi file to deploy the package on the server.
C.
Open a command prompt and execute the package by using the SQL Log provider and
running the dtexecui.exe uti
D.
Create a reusable custom logging component and use it in the SSIS project.
E.
Open a command prompt and run the dtutil /copy command.
F.
Configure the SSIS solution to use the Project Deployment Model.
G.
Add an OnError event handler to the SSIS project.
H.
Open a command prompt and run the gacutil command.
I.
Open a command prompt and run the dtexec /dumperror /conn command.
J.
Open a command prompt and run the dtexec /rep /conn command.
K.
Configure the output of a component in the package data flow to use a data tap.
Explanation:
http://msdn.microsoft.com/en-us/library/ms141212.aspx
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-
2012-part-1-of-2/
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-
2012-part-2-of-2/
C
0
0
F with project deployment you don’t need to configure logging.
0
0
C
0
0
I Will go with F too
0
0
F also achieve requirement of logging. But question stated that troubleshooting an existing SSIS package and your solution must be minimize deployment and development efforts.
So C is the best choice of answer.
0
0
C
https://msdn.microsoft.com/en-us/library/ms141212(v=sql.120).aspx
https://msdn.microsoft.com/en-us/library/hh231187(v=sql.120).aspx
0
0