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/ms180378(v=sql.110).aspx
F.
1
0
Correct Ans will be, i think (J)
0
0
yes, it should be J
0
0
agree, it’s J
0
0
Every aspect can accomplished by simply using the new SSISDB catalog. The minimal deployment and development effort would be deploying it there.
I agree with Noel: F
0
0
F
0
0
F is correct
0
0