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.
Use an msi file to deploy the package on the server.
C.
Open a command prompt and run the gacutil command.
D.
Open a command prompt and run the dtutil /copy command.
E.
Open a command prompt and run the dtexec /rep /conn command.
F.
Open a command prompt and run the dtexec /dumperror /conn command.
G.
Run the package by using the dtexecui.exe utilityand the SQL Log provider.
H.
Create a reusable custom logging component and use it in the SSIS project.
I.
Configure the SSIS solution to use the Project Deployment Model.
J.
Configure the output of a component in the package data flow to use a data tap.
K.
Run the dtutil command to deploy the package to the SSIS catalog and store the configuration in SQL
Server.
Explanation:
According to these references, this answer looks correct.
References:
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
Again…looking for one answer and K has nothing to do with this question! Maybe it’s a bug on the page, but seems to be a pattern with this line of questions.
Per MSDN:
Data Flow Taps
SQL Server 2012 Other Versions
You can add a data flow tap to a path that connects two data flow components in an SSIS
package (data flow path) and direct the output from the data flow tap to an external file at runtime. This feature allows you to inspect data in the following stages of ETL (Extract-Transform-Load) processing:
After the data is extracted from a data source.
Before and after the data is transformed.
Before the data is loaded into its destination.
You must deploy your SSIS packages by using the project deployment model (not the package deployment model) to take advantage of this feature.
Add a data flow tap
After you deploy your SSIS project using the project deployment model to the Integration Services (SSIS) Catalog, you use the catalog.add_data_tap (or) catalog.add_data_tap_by_guid stored procedures in the SSISDB database to add a data flow tap before starting an execution instance. At present, a data tap can only be added by executing these stored procedures; there is no user interface support for adding data flow taps. However, you can generate statements for creating and starting an execution instance by using the SQL Server Management Studio and then add a add_data_tap (or) add_data_tap_by_guid statement to the generated script. The following procedure provides the detailed steps to add a data tap.
J) data tap
It truly is nearly extremely difficult to encounter well-qualified users on this niche, regrettably you seem like you fully understand what exactly you’re writing about! Thank You
http://shur-lock.tumblr.com
Having read this I believed it was extremely enlightening. I appreciate you taking the time and effort to put this article together. I once again find myself spending a lot of time both reading and leaving comments. But so what, it was still worthwhile!|
Configure the output of a component in the package data flow to use a data tap.