Microsoft
70-463 · Question #42
70-463 Question #42: Real Exam Question with Answer & Explanation
The correct answer is J: Run the package by using the dtexecui.exe utility and the SQL Log provider.. Using dtexecui.exe with the SQL Log provider enables package logging through a GUI with no code changes or deployment required, minimizing both development and deployment effort.
Question
Occasionally a job that executes an existing SQL Server Integration Services (SSIS) package does not complete and nothing is processed. You need to ensure that package logging occurs. Your solution must minimize deployment and development efforts. What should you do?
Options
- ACreate a reusable custom logging component.
- BUse the gacutil command.
- CUse the Project Deployment Wizard.
- DRun the package by using the dtexec/rep/conn command.
- EAdd a data tap on the output of a component in the package data flow.
- FCreate an OnError event handler.
- GUse the dtutil/copy command.
- HDeploy the package by using an msi file.
- IRun the package by using the dtexec/dumperror/conn command.
- JRun the package by using the dtexecui.exe utility and the SQL Log provider.
Explanation
Using dtexecui.exe with the SQL Log provider enables package logging through a GUI with no code changes or deployment required, minimizing both development and deployment effort.
Common mistakes.
- A. Creating a reusable custom logging component requires significant development effort, directly violating the constraint to minimize development work.
- B. gacutil.exe registers .NET assemblies in the Global Assembly Cache and is used for deploying custom components, not for configuring package logging.
- C. The Project Deployment Wizard is used to deploy SSIS projects to the SSIS catalog and does not configure logging for packages.
- D. dtexec with /rep creates a report file but does not establish persistent SQL-based logging and does not use the SQL Log provider.
- E. A data tap captures data flow output to a file and is used to inspect data in transit, not to log package-level execution events.
- F. Creating an OnError event handler requires opening and modifying the package in SSDT, incurring development and redeployment effort.
- G. dtutil /copy is used to copy SSIS package files between storage locations and has no logging functionality.
- H. Deploying via an MSI file is a deployment method, not a logging configuration, and still requires redeployment effort.
- I. dtexec /dumperror generates memory dump files on errors for debugging, not structured execution logs suitable for auditing or monitoring.
Concept tested. SSIS package logging using dtexecui with SQL Log provider
Community Discussion
No community discussion yet for this question.