Optimization and Integrity tasks created in a SLS 4.8.4 maintenance plan
are using xp_slssqlmaint instead of xp_sqlmaint and failing as part of
the Maintenance Plan. The backup task will complete, but due to the
failing tasks, the maintenance plan reports failure.
How do the LiteSpeed Integrity Check Wizard and Integrity Checks included in Maintenance Plans work?
Can these steps be run via script in Query Analyzer?
Product Defect
Fixed in Version 5.0.0.1060 of LiteSpeed.
The DBCC CHECKDB command, as well as ALL_ERRORMSGS, TABLOCK , ESTIMATEONLY , PHYSICAL_ONLY , REPAIR_FAST are native SQL Server commands.
WORKAROUND: Schedule optimization and Integrity Check jobs as Native SQL Server jobs. LiteSpeed maintenance plans may be created with a SQL Task and the native t-sql inserted. See examples of native scripts below.
For additional information, see http://msdn2.microsoft.com/en-us/library/ms176064.aspx
SQL T-SQL which is similar to the function called by the LiteSpeed GUI screens:
DBCC CHECKDB
[
[ ( 'database_name' | database_id | 0
[ , NOINDEX
| , { REPAIR_FAST } ]
) ]
[ WITH
{
[ ALL_ERRORMSGS ]
[ , NO_INFOMSGS ]
[ , TABLOCK ]
[ , ESTIMATEONLY ]
[ , { PHYSICAL_ONLY } ]
}
]
]
