With your maintenance plan open in the Design tab, click to configure reports about execution of the entire maintenance plan and set the reporting and logging options. A report contains information about each task within one subplan: task name, duration, results.
Review the following for information about logging in Maintenance Plans:
|Write a text file report in directory||
Select a directory in which to write a text file report. Alternately select to browse and locate a directory
|Write an html file report in directory||
Select a directory in which to write an html file report. Alternately select to browse and locate a directory.
|Send report to an email recipient||
Select to send an email report to a designated recipient.
|Log extended information||
Logs plan details in msdb.dbo.sysmaintplan_logdetail for both LiteSpeed and native SQL Server SSIS maintenance plans, for all tasks. This additional information is task-specific
For the native SQL Server plans, this information also becomes a part of the native reporting and may increase the size of the stored maintenance plan history.
|Log to remote Server||Writes the plan history to the remote server. Select the connection drop-down to choose the server. Alternately assign a new server.|
Logs LiteSpeed maintenance plan utility activity.
Quest Software support may ask you to enable debug logging in maintenance plans to help troubleshoot product issues. Make sure LiteSpeed is installed on the server where you have a problem with maintenance plans.
When a subplan is executed, the Maintenance Plan engine saves the archived <plan_name>_<subplan_name>[<GUID>].zip file in the default
Each archive has:
LiteSpeed's debug logging is not supported for the native SQL Server tasks. If the Use LiteSpeed option is cleared for a task, then that task is handled by the native SQL Server components.