-
Title
Whydo legacy plans include a Planid but non-legacy plans do not? -
Description
Only legacy plans include a Planid in TSQL. Non-legacy plans do not.
Example:
execute master.dbo.xp_slssqlmaint N'-PlanID F3D7F40C-AC85-4E94-9EF6-BC4A01CE3D88 -BkUpMedia DISK -BkUpDB -UseDefDir -BkExt "bak" -NOOPTOLR -CompressionLevel 2 -Logging 0 -Default "%D_%T_%Y-%m-%d-%H%M%S.%EXT%" -Exclude Offline LogShippng '-vs.-
The databases to be backed up are listed individually or as "All user databases"
execute master.dbo.xp_slssqlmaint N'--D "Northwind" "AdventureWorks" "AdventureWorksDW" -BkUpMedia DISK -BkUpDB -UseDefDir -BkExt "bak" -NOOPTOLR -CompressionLevel 2 -Logging 0 -Default "%D_%T_%Y-%m-%d-%H%M%S.%EXT%" -Exclude Offline LogShippng -
Cause
Design feature
-
Resolution
Only legacy plans include a Planid in TSQL. Non-legacy plans do not.
This is a design feature to faciliatate the copying of Maintenance Plan from one server to another. When "all user databases" is chosen and that is the text in the tsql command, the Litespeed application will go thru the sysdatabases table and select the user databases for backup.
The LiteSpeed for SQL Server Maintenance Plan works the same from the command line for both the legacy and the SSIS plans. The PlanID is not a requirement for SSIS.
You could add these additional parameters if Maintenance Plan reporting is required. the "RUNID" is retrieved from msdb.dbo.sysmaintplan_logdetail.task_detail_id-RunId "DFB65168-ACDA-42B3-A8D2-4543C3FE3FB5" "Back Up Database 1"" -NO_OUTPUT ErrorPipe error_1306667720_18724_19422_1779289040