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.
Deploy the package by using an msi file.
B.
Use the gacutil command.
C.
Create an OnError event handler.
D.
Create a reusable custom logging component.
E.
Use the dtutil /copy command.
F.
Use the Project Deployment Wizard.
G.
Run the package by using the dtexec /rep /conn command.
H.
Add a data tap on the output of a component in the package data flow.
I.
Run the package by using the dtexec /dumperror /conn command.
J.
Run the package by using the dtexecui.exe utility and the SQL Log provider.
K.
Deploy the package to the Integration Services catalog by using dtutil and use SQL
Server to store the configuration.
Explanation:
http://msdn.microsoft.com/en-us/library/ms140246.aspx
http://msdn.microsoft.com/en-us/library/hh231187.aspx
J
F
SSIS Catalog support all the listed requerments by default
agreed
I can’t believe it’s F. F is a partial solution because while the Project can provide logging details with all the niceties attached, it will only do it if the logging requirements are set in the individual packages, tasks etc. in ssdt while the project is being designed. With J you’ll get logging of some sort or another, so it seems like a complete solution. So of course the answer must be F.
Also J is 32 bit and yesteryear so this is a way for MSFT to get us all to embrace their new fake solution.
58 v3
http://www.aiotestking.com/microsoft/you-need-to-configure-a-logging-methodology-that-meets-the-requirements-while-minimizing-the-amount-of-deployment-and-development-effort-9/
This is similar. The only real difference between the two is this requirement:
Automatic purge of older log entries
Configurable log details
vs.
Log archival must be automated.
Log details can be configured on execution on both F and J. logs are automatically purged within ssisdb, I believe. Not so with the integration services logging. So, here, it must be F
F.
Use the Project Deployment Wizard.