PrepAway - Latest Free Exam Questions & Answers

You need to ensure that package logging occurs

You are troubleshooting an existing SQL Server Integration Services (SSIS) package. On several occasions,
the package execution does not finish and no data seems to have been transferred. You need to ensure that
package logging occurs. Your solution must minimizedeployment and development efforts. What should you
do?

PrepAway - Latest Free Exam Questions & Answers

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://msdn.microsoft.com/en-us/library/ms141212.aspx
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-2-of-2/

26 Comments on “You need to ensure that package logging occurs

  1. pb7788 says:

    Looks like it’s A:

    Troubleshooting Tools for Package Execution

    SQL Server 2012 Other Versions

    Integration Services includes features and tools that you can use to troubleshoot packages when you execute them after they have been completed and deployed.
    At design time, SQL Server Data Tools (SSDT) provides breakpoints to pause package execution, the Progress window, and data viewers to watch your data as it passes through the data flow. However, these features are not available when you are running packages that have been deployed. The main techniques for troubleshooting deployed packages are as follows:

    – ***Catch and handle package errors by using event handlers.***
    – Capture bad data by using error outputs.
    – Track the steps of package execution by using logging.

    You can configure the event handler container in the following ways:
    Specify a name and description for the event handler.
    Indicate whether the event handler runs, whether the package fails if the event handler fails, and the number of errors that can occur before the event handler fails.
    Specify an execution result to return instead of the actual execution result that the event handler returns at run time.
    Specify the transaction option for the event handler.
    ***Specify the logging mode that the event handler uses.***




    0



    0

Leave a Reply