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:
References:
http://msdn.microsoft.com/en-us/library/ms140246.aspxhttp://msdn.microsoft.com/en-us/library/hh231187.aspx
Only J
0
0
only J as dbo says
0
0
Am I right in thinking that by using the Project Deployment model, this in turn requires the SSISDB catalog which in turn provides the t-sql and report access required? It seems logical now. At first I didn’t twig the connection!
0
0
Right here is the right site for anyone who would like to find out about this topic. You know so much its almost hard to argue with you (not that I really would want to…HaHa). You certainly put a new spin on a topic that has been written about for many years. Excellent stuff, just excellent!|
0
0
}
0
0