70-463 · Question #210
70-463 Question #210: Real Exam Question with Answer & Explanation
The correct answer is C. Use an event handler for OnTaskFailed for the package.. The key constraint is that the T-SQL script must execute exactly once per failed data flow task, regardless of how many individual errors that task generated. The OnError event fires once for EACH error within a task - so a task that generates three errors would trigger OnError t
Question
Options
- AUse an event handler for OnError for the package.
- BUse an event handler for OnError for each data flow task.
- CUse an event handler for OnTaskFailed for the package.
- DView the job history for the SQL Server Agent job.
- EView the All Messages subsection of the All Executions report for the package.
- FStore the System::SourceID variable in the custom log table.
- GStore the System::ServerExecutionID variable in the custom log table.
- HStore the System::ExecutionInstanceGUID variable in the custom log table.
- IEnable the SSIS log provider for SQL Server for OnError in the package control flow.
- JEnable the SSIS log provider for SQL Server for OnTaskFailed in the package control flow.
Explanation
The key constraint is that the T-SQL script must execute exactly once per failed data flow task, regardless of how many individual errors that task generated. The OnError event fires once for EACH error within a task - so a task that generates three errors would trigger OnError three times, causing the T-SQL script to run three times. OnTaskFailed, by contrast, fires exactly once per task failure, no matter how many errors occurred inside it. By attaching the OnTaskFailed event handler at the package level (C), it will catch failures from all data flow tasks within the package, and the handler fires only once per failing task, satisfying both requirements. Option B (OnError per data flow task) would still fire multiple times if multiple errors occur within a single task.
Topics
Community Discussion
No community discussion yet for this question.