while running the following query:
-- DATEADD (datepart , number , date ) DECLARE @dt DATETIME SELECT @dt = DATEADD(month,-6,getdate()) select @dt EXEC msdb.dbo.sp_delete_backuphistory @oldest_date = @dt
I get lots of locks and blocks, possibly because this command has not been run for a while, if ever.
Is there a way to find out how much is there to delete in each of the involved tables, before I actually run or plan to run this command?
I use dateadd to calculate 6 months.
Within sp_delete_backuphistory the following tables are trimmed:
sp_delete_backuphistory must be run from the msdb database and affects the following tables: