-
Title
Why are there several Report or Log Files from Maintenance Plan Job? -
Description
Why are there several Report Files from Maintenance Plan Job? When Maintenance Plan logging is turned on, several files are generated and zipped into a folder, or placed in the default log folder: C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed. In Windows Vista® and Windows Server® 2008, the default location of user data has changed. An example of this change is the Documents and Settings directory, which has been moved from %systemdrive%\Documents and Settings to %systemdrive%\Users.
-
Resolution
From the LiteSpeed for SQL Server Help File:
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. To view the details, right-click the plan in Management Studio and select View History. Expand the row, click the sub-line and view additional information in the Task detail field.
- Log to remote Server—Writes the plan history to the remote server.
Debug Logging—Logs LiteSpeed maintenance plan utility activity.
Quest Support may ask you to enable debug logging in maintenance plans to help troubleshoot product issues. Make sure you have LiteSpeed for SQL Server installed on the server where you have a problem with the maintenance plan, open the plan in the Design tab, click
and set the debug logging level.
When a subplan is executed, the Maintenance Plan engine saves the archived <plan_name>_<subplan_name>[<GUID>].zip file in the default output directory.
Each archive has:
- one or more files for all LiteSpeed tasks in a subplan, including the Reporting task,
- one file containing -Gather command-line command to collect statistics,
- one file containing -CollectStats command-line command for the process that starts collecting statistics to repositories (only created for SSIS plans).
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.
Backup activity: Additionally, you can configure logging in the Backup Database and Fast Compression Backup tasks to log LiteSpeed backup activity. See Set LiteSpeed Options for more information.