To ease the debugging of packages, you standardize the SQL Server Integration Services (SSIS) package
logging methodology. The methodology has the following requirements:
Centralized logging in SQL Server
Simple deployment
Availability of log information through reports or T-SQL
Automatic purge of older log entries
Configurable log details
You need to configure a logging methodology that meets the requirements while minimizing the amount of
deployment and development effort. What should you do?
A.
Use the gacutil command.
B.
Use the dtutil /copy command.
C.
Use the Integration Services 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 utilityand 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.
Explanation:
According to these references, this answer looks correct.
References:
http://msdn.microsoft.com/en-us/library/ms140246.aspx
http://msdn.microsoft.com/en-us/library/hh231187.aspx
H.
Run the package by using the dtexecui.exe utility and the SQL Log provider.
0
0
what a crappy question. it asks to configure a methodology, whereas the most likely answer (H) is a recurrent execution action, not configuration.
0
0
C
0
0
I agree with C
0
0
H is corect
0
0
I was thinking first of answer C as it promotes the use of the new Project deployment model. dtexecui.exe can only be used for 32 bit legacy package deployment model and cannot execute packages on the new SSISBD catalog. When deploying using the project model there are standard reports available and purging of operation log can be set for the SSISDB database.
A reason why Answer H could be right is that it includes the SQL Log Provider, which is centralized, simple to deploy. I guess the reports need to be created on the sysssislog table. Automatic purging of this table, not to sure about, but probably need to write a T-SQL script and run it as a re-occuring job. Log details can then be configured during design time of the package.
So which one is the correct answer?
0
0
The answer is definitely H. With the DTEXECUI you can choose which log provider to use:Text Files, SQL Server, SQL Server Profiler, Windows Event Log, XML Files
0
0
C
0
0
It’s C because H doesn’t automatically purge old log entries
0
0
C
0
0