You need to configure a logging methodology that meets the requirements while minimizing the amount of deployment and development effort

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?

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:
References:
http://msdn.microsoft.com/en-us/library/ms140246.aspx
http://msdn.microsoft.com/en-us/library/hh231187.aspx



Leave a Reply 4

Your email address will not be published. Required fields are marked *


John Sno

John Sno

It should be F
dtexec /dumperror /conn command does not exist should be dumpOnError
dtexecui.exe utility and the SQL Log provider can only be used if the package is already deployed to a file system

Shoaib

Shoaib

F is the correct answer

henrov

henrov

Me too, F it is.

(Seeing I as the right answer for a split-second made me doubt everything I learned, causing a desperate, sinking feeling and the urge to crawl in the smallest corner of my room and sob uncontrollably while cursing all the gods in the Pantheon)