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?
A. Execute the catalog.add_data_tap stored procedure with the package execution_id.
B. Execute the catalog.create_execution_dump stored procedure with the package execution_id.
C. Run the DTEXEC utility with the /DumpOnError option.
D. Run the DTEXEC utility with the /Reporting V option.
/DumpOnError
(Optional) Creates the debug dump files, .mdmp and .tmp, when any error occurs while the package is running.
By default, Integration Services stores the debug dump files in the folder, :Program FilesMicrosoft SQL Server100SharedErrorDumps folder.
https://technet.microsoft.com/en-us/library/ms162810(v=sql.105)
/Dumperror code
(Optional) Creates the debug dump files, .mdmp and .tmp, when one or more specified events occur while the package is running. The error code argument specifies the type of event code—error, warning, or information—that will trigger the system to create the debug dump files. To specify multiple event codes, separate each error code argument by a semi-colon (;).
By default, Integration Services stores the debug dump files in the folder, :Program FilesMicrosoft SQL Server100SharedErrorDumps.
https://technet.microsoft.com/en-us/library/ms162810(v=sql.105)