nerdexam
Exams70-463Questions#209
Microsoft

70-463 · Question #209

70-463 Question #209: Real Exam Question with Answer & Explanation

The correct answer is E: View the All Messages subsection of the All Executions report for the package.. Because the package runs under the SSIS Catalog (Project Deployment Model) with basic logging, all execution history - including error messages - is automatically persisted in the catalog's internal tables. The 'All Executions' report in SSMS surfaces this history, and its 'All M

Question

You administer a SQL Server Integration Services (SSIS) solution in the SSIS catalog. A SQL Server Agent job is used to execute a package daily with the basic logging level. Recently, the package execution failed because of a primary key violation when the package inserted data into the destination table. You need to identify all previous times that the package execution failed because of a primary key violation. What should you do?

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

Because the package runs under the SSIS Catalog (Project Deployment Model) with basic logging, all execution history - including error messages - is automatically persisted in the catalog's internal tables. The 'All Executions' report in SSMS surfaces this history, and its 'All Messages' subsection shows the detailed error messages (including the exact primary key violation text) for every past execution. This lets you filter for all historical runs that failed with that specific error without any additional setup. Options like enabling additional log providers (I, J) or event handlers (A, B, C) only affect future executions and cannot reveal what happened in past runs. Viewing the SQL Agent job history (D) shows job-level success/failure but not the specific SSIS error message text.

Community Discussion

No community discussion yet for this question.

Full 70-463 Practice