70-463 · Question #151
You develop a SQL Server Integration Services (SSIS) project by using the Package Deployment Model. A package in the project extracts data from a Windows Azure SQL Database database. The package is…
The correct answer is C. Run the DTEXEC utility with the /DumpOnError option. In the Package Deployment Model, packages are executed using the DTEXEC command-line utility rather than through the SSISDB catalog. The /DumpOnError option instructs DTEXEC to generate .mdmp (mini-dump) and .tmp debug files when the package encounters an error, enabling…
Question
You develop a SQL Server Integration Services (SSIS) project by using the Package Deployment Model. A package in the project extracts data from a Windows Azure SQL Database database. The package is deployed to SQL Server. The package is not producing the desired results. You need to generate the .mdmp and .tmp debug files in order to troubleshoot the issues. What should you do?
Options
- AExecute the catalog.add_data_tap stored procedure with the package execution_id.
- BExecute the catalog.create_execution_dump stored procedure with the package execution_id.
- CRun the DTEXEC utility with the /DumpOnError option.
- DRun the DTEXEC utility with the /Reporting V option.
How the community answered
(29 responses)- A7% (2)
- C90% (26)
- D3% (1)
Explanation
In the Package Deployment Model, packages are executed using the DTEXEC command-line utility rather than through the SSISDB catalog. The /DumpOnError option instructs DTEXEC to generate .mdmp (mini-dump) and .tmp debug files when the package encounters an error, enabling post-mortem debugging. Option B (catalog.create_execution_dump) is only valid in the Project Deployment Model, which uses the SSISDB catalog - it does not apply here. Option A (catalog.add_data_tap) captures data flowing through a pipeline component at runtime, which is unrelated to generating crash dump files. Option D (/Reporting V) enables verbose console logging of events but does not produce binary debug dump files.
Topics
Community Discussion
No community discussion yet for this question.