To facilitate the troubleshooting of SQL Server Integration Services (SSIS) packages, a
logging methodology is put in place.
The methodology has the following requirements:
The deployment process must be simplified.
All the logs must be centralized in SQL Server.
Log data must be available via reports or T-SQL.
Log archival must be automated.
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.
Open a command prompt and run the gacutil command.
B.
Open a command prompt and execute the package by using the SQL Log provider and
running the dtexecui.exe utility.
C.
Add an OnError event handler to the SSIS project.
D.
Use an msi file to deploy the package on the server.
E.
Configure the output of a component in the package data flow to use a data tap.
F.
Run the dtutil command to deploy the package to the SSIS catalog and store the
configuration in SQL Server.
G.
Open a command prompt and run the dtexec /rep /conn command.
H.
Open a command prompt and run the dtutil /copy command.
I.
Open a command prompt and run the dtexec /dumperror /conn command.
J.
Configure the SSIS solution to use the Project Deployment Model.
K.
Create a reusable custom logging component and use it in the SSIS project.
Explanation:
http://msdn.microsoft.com/en-us/library/ms140246.aspxhttp://msdn.microsoft.com/en-us/library/hh231187.aspx
j
Only ‘J’.
I think it could be B or J. B is the go to answer if you need logging with package deployment. The question clearly says packages, not projects. J would only be the answer if you redeploy the packages as projects, but MSFT is such a stickler with whether we’re dealing with a package or a project or have an option to redeploy the packages as projects it’s really unclear here which answer is correct. In real life, we’d of course redeploy the packages as projects and use the tsql items.
Another issue is that the question is asking to configure a logging methodology. None of the choices actually configure a logging methodology. Certainly not using the project deployment wizard. You can configure logging in SSDT by setting logging properties and attaching logging tasks to events. You can also configure logging levels on execution by setting the logging level:
https://msdn.microsoft.com/en-us/library/hh231191.aspx
Executing the package in SSMS or integration services or with dtexecui seem like the only option to configure logging, though not really. Overall this is a crap question.
J
The only solution that will allow us to exploit log files through reports is Answer J, due to the fact in Integration Services Catalogs we can generate “All executions reports” to troubleshoot a SSIS solution.