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?
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/
Are you sure that answer A is correct? Shouldn’t it be answer I: “Configure the SSIS solution to use the Project Deployment Model”?
I agree with Matt, it says that the execution does not finish not that an error occurs
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.***
Although websites we backlink to below are considerably not related to ours, we feel they are essentially really worth a go by, so have a look.
Just beneath, are many completely not associated sites to ours, nonetheless, they’re surely really worth going over.
We like to honor lots of other net internet sites on the web, even though they arent linked to us, by linking to them. Underneath are some webpages really worth checking out.
Wonderful story, reckoned we could combine a few unrelated data, nevertheless really really worth taking a search, whoa did 1 learn about Mid East has got much more problerms as well
although web sites we backlink to below are considerably not connected to ours, we feel they are basically really worth a go by, so possess a look
Here is a good Weblog You might Uncover Interesting that we Encourage You
just beneath, are numerous totally not associated web pages to ours, on the other hand, they are surely worth going over
we came across a cool site that you simply might get pleasure from. Take a look in case you want
we like to honor lots of other world wide web sites around the internet, even if they arent linked to us, by linking to them. Beneath are some webpages worth checking out
Here are several of the web sites we advocate for our visitors
although internet websites we backlink to below are considerably not related to ours, we feel they’re really really worth a go by way of, so possess a look
Here are some of the web sites we suggest for our visitors
check beneath, are some absolutely unrelated websites to ours, nonetheless, they may be most trustworthy sources that we use
below youll locate the link to some web-sites that we believe you must visit
Every after inside a though we select blogs that we read. Listed below are the latest sites that we select
Sites of interest we’ve a link to
just beneath, are many completely not connected web sites to ours, on the other hand, they’re surely really worth going over
please visit the websites we comply with, including this one, because it represents our picks through the web
just beneath, are several completely not associated web sites to ours, on the other hand, they’re surely worth going over
one of our visitors not too long ago recommended the following website
It’s G, not A.
Run the package by using the dtexecui.exe utility and the SQL Log provider.
G. You have to ensure that logging occurs. Adding on error event helps with troubleshooting not with logging.