You are implementing a SQL Server Integration Services (SSIS) package that loads data
hosted in a SQL Azure database into a data warehouse.
The source system contains redundant or inconsistent data. When the package finds invalid
data, the row containing the invalid data must be omitted but it must also be written to a text
file for further analysis.
You need to establish the best technique to log these invalid rows while keeping the amount
of development effort to a minimum.
What should you do?
A.
Add an OnError event handler to the SSIS project.
B.
Open a command prompt and execute the package by using the SQL Log provider and
running the dtexecui.exe utility.
C.
Use an msi file to deploy the package on the server.
D.
Open a command prompt and run the gacutil command.
E.
Run the dtutil command to deploy the package to the SSIS catalog and store the
configuration in SQL Server.
F.
Open a command prompt and run the dtutil /copy command.
G.
Create a reusable custom logging component and use it in the SSIS project.
H.
Configure the SSIS solution to use the Project Deployment Model.
I.
Configure the output of a component in the package data flow to use a data tap.
J.
Open a command prompt and run the dtexec /rep /conn command.
K.
Open a command prompt and run the dtexec /dumperror /conn command.
Explanation:
http://technet.microsoft.com/en-us/library/hh230989.aspx
http://www.rafael-salas.com/2012/01/ssis-2012-quick-peek-to-data-taps.html
http://msdn.microsoft.com/en-us/library/ms162820.aspx
http://msdn.microsoft.com/en-us/library/hh231187.aspx
http://technet.microsoft.com/en-us/library/ms140223.aspx
http://msdn.microsoft.com/en-us/library/jj655339.aspx
Here’s another controversial one similar to an earlier question. Is it data taps or custom component?
Incidentally, you don’t configure a component to use a data tap. You attach a data tap to a component after the package is deployed and ready for use, no?
Here G is rewritten slightly from earlier versions where the answer is custom component instead of custom logging component. Obviously a custom logging component won’t invalidate rows, so G can’t be the answer like a normal custom component
“while keeping the amount of development effort to a minimum”, thats why I choose “I”
Data taps cannot be defined at design time.