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
Correct option (for above scenario) is: F
If you desire to have complete/comprehensive logging to aid troubleshooting of the package, your best bet is to use the Project Deployment Model. It tidies up a lot of under-the-hood stuff for you; gives you multiple logging options -basic, performance, verbose, etc. And you can always drill down through it’s log to find info about likely SSIS-package component failure, and resolve the errors.
Agree. F
This is an age old question that no one agrees with because it’s a bad question
http://www.aiotestking.com/microsoft/you-need-to-ensure-that-package-logging-occurs/
There’s even an earlier version of this question in this packet that is different only in the order of the answers. Who knows if it’s F or C. C is easier.
I would choose C as minimise deployment
and development efforts. just create a SQL Log table and modify SQL Agent Job to execute the package with SQL Provider Logging.
if F, we have to go through the package to check package level connections, variables in SSDT then deploy , configure and setup batch job to run the package with right environment.
would that be troublesome?