-
Título
We installed LiteSpeed on a server that already has an existing sql maintenance plan configured. Will LiteSpeed use that native sql maintenance plan? How to confirm? -
Descripción
We installed LiteSpeed on a server that already has an existing sql maintenance plan configured. Will LiteSpeed use that native sql maintenance plan?
How do we confirm whether LiteSpeed is now managing the maintenance plan or if the SQL Server native is still executing it independent of LiteSpeed.
How do we determine whether it is a LiteSpeed created-maintenance plan or a native maintenance plan that is being run? -
Resolución
LiteSpeed hooks into any pre-existing maintenance plans on the SQL Server. And vice versa--any maintenance plans you create within the LiteSpeed console will show up in the SQL Server SSMS UI as well.And note that the SSMS UI and the LiteSpeed Console UI have an almost identical scheduling dialog window. All the options are the same and the GUI layout is almost the same. And any configuration you do in one UI will update the other.To confirm that it really is LiteSpeed that is managing the backup job, go to the maintenance plan in the LiteSpeed console UI and double click on the Task in question. And that will open up a dialog window like you see in the attached screenshots. Then click on the 'View T-SQL' button on the the lower left.The screenshot1.jpg is of a native SQL script and screenshot2.jpg is of a LiteSpeed script. Screenshot2 is using the LiteSpeed extended stored procedure 'xp_slssqlmaint'.You can determine if it is native sql or LiteSpeed by whether the 'Use LiteSpeed' checkbox is checked or not. If it is not checked, a native SQL script is used. And when it is checked, the script will become a LiteSpeed script, using 'xp_slssqlmaint'.When it is a LiteSpeed maintenance plan, some of the options on those LiteSpeed Console UI screens became enabled that are greyed out when its a native maintenance plan. These are additional options that LiteSpeed gives you, such as the 'Compression Level' (shown in screenshot3).The 'Convert to LiteSpeed' button will convert a native maintenance plan into a LiteSpeed maintenance plan. When you click the 'Convert to LiteSpeed' button, you need to first press the 'Refresh' button and then the 'Save Plan' for the plan to really be a LiteSpeed plan and 'Use LiteSpeed' to be enabled. Otherwise, the change doesn't seem to "take".
There is another way to determine if a backup file had been created by LiteSpeed or is a native-created backup file. And this will work even if it the backup was created by a job, for example, not necessarily a maintenance plan.
To do so, run a T-SQL script in the SSMS, using the xp_file_search extended stored procedure. Like the below, for example:exec master.dbo.xp_file_search @filename = 'C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Backup\msdb_backup_2019_08_27_184206_0056918.bak
Attached is a screenshot (xp_file_search_screenshot1.jpg) of the output of that run of the above. Note that the 'FormatType' field is "3", that indicates a native backup. When the 'FormatType' field is "2", that is a Litespeed-created backup (like in xp_file_search_screenshot2.jpg).