How to minimizeplan ahead the effect of running sp_delete_backuphistory? Measure the gains too!












2















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.



enter image description here



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:



backupfile



backupfilegroup



backupmediafamily



backupmediaset



backupset



restorefile



restorefilegroup



restorehistory











share|improve this question


















  • 1





    The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

    – EzLo
    49 mins ago











  • @EzLo thank you for the link MSDB Performance Tuning

    – marcello miorelli
    34 mins ago
















2















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.



enter image description here



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:



backupfile



backupfilegroup



backupmediafamily



backupmediaset



backupset



restorefile



restorefilegroup



restorehistory











share|improve this question


















  • 1





    The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

    – EzLo
    49 mins ago











  • @EzLo thank you for the link MSDB Performance Tuning

    – marcello miorelli
    34 mins ago














2












2








2








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.



enter image description here



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:



backupfile



backupfilegroup



backupmediafamily



backupmediaset



backupset



restorefile



restorefilegroup



restorehistory











share|improve this question














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.



enter image description here



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:



backupfile



backupfilegroup



backupmediafamily



backupmediaset



backupset



restorefile



restorefilegroup



restorehistory








sql-server backup delete scripting monitoring






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 1 hour ago









marcello miorellimarcello miorelli

5,9802163143




5,9802163143








  • 1





    The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

    – EzLo
    49 mins ago











  • @EzLo thank you for the link MSDB Performance Tuning

    – marcello miorelli
    34 mins ago














  • 1





    The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

    – EzLo
    49 mins ago











  • @EzLo thank you for the link MSDB Performance Tuning

    – marcello miorelli
    34 mins ago








1




1





The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

– EzLo
49 mins ago





The msdb database doesn't have indexes on the system tables, so if you had many backup/restore operations over time, purging records might take long. I don't know how to see the records to delete beforehand, but you can try creating indexes as suggested in the following post and doing your purge in batches (with very old dates first, then closer to last 6 months). weblogs.sqlteam.com/geoffh/2008/01/21/msdb-performance-tuning

– EzLo
49 mins ago













@EzLo thank you for the link MSDB Performance Tuning

– marcello miorelli
34 mins ago





@EzLo thank you for the link MSDB Performance Tuning

– marcello miorelli
34 mins ago










2 Answers
2






active

oldest

votes


















3














My gripes with this proc go back a long way:




  • The Annals of Hilariously Bad Code, Part 1: Critique the Code

  • The Annals of Hilariously Bad Code, Part 2


The problem you run into when deleting large amounts of data is the crappy estimate you get from the table variables.



I've had pretty good luck creating a new version of the proc using temp tables. You could also try just adding recompile hints, but hey, this way we get useful indexes.



As a side note: if you still run into this blocking because this is running long, you can try either removing the transaction code, or changing it to encapsulate each individual delete (though at that point the benefits are negligible).



CREATE   PROCEDURE [dbo].[sp_delete_backuphistory_pro]
@oldest_date datetime
AS
BEGIN
SET NOCOUNT ON

CREATE TABLE #backup_set_id (backup_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #media_set_id (media_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #restore_history_id (restore_history_id INT PRIMARY KEY CLUSTERED)

INSERT INTO #backup_set_id WITH (TABLOCKX) (backup_set_id)
SELECT DISTINCT backup_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #media_set_id WITH (TABLOCKX) (media_set_id)
SELECT DISTINCT media_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #restore_history_id WITH (TABLOCKX) (restore_history_id)
SELECT DISTINCT restore_history_id
FROM msdb.dbo.restorehistory
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)

BEGIN TRANSACTION

DELETE FROM msdb.dbo.backupfile
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupfilegroup
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefile
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefilegroup
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorehistory
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupset
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediafamily
FROM msdb.dbo.backupmediafamily bmf
WHERE bmf.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bmf.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediaset
FROM msdb.dbo.backupmediaset bms
WHERE bms.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bms.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

COMMIT TRANSACTION
RETURN

Quit:
ROLLBACK TRANSACTION

END





share|improve this answer





















  • 1





    +1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

    – marcello miorelli
    11 mins ago











  • @marcellomiorelli 😂

    – Erik Darling
    8 mins ago



















1














Here is something you could try.




  • Restore a backup of your MSDB database to a test server and call it
    something like MSDB_TEST.

  • Once restored, go into the sp_delete_backuphistory stored procedure
    in the MSDB_TEST database and search/replace msdb. with
    msdb_test. and alter it.

  • Capture the current row count of the tables you are interested in.

  • Now, run the altered version of the sp_delete_backuphistory stored procedure in the MSDB_TEST database.

  • Compare the current row counts to the previously capture ones.






share|improve this answer
























  • +1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

    – marcello miorelli
    32 mins ago








  • 1





    @marcellomiorelli - understood - I'm afraid that's all I have for this problem.

    – Scott Hodgin
    28 mins ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233375%2fhow-to-minimize-plan-ahead-the-effect-of-running-sp-delete-backuphistory-measur%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









3














My gripes with this proc go back a long way:




  • The Annals of Hilariously Bad Code, Part 1: Critique the Code

  • The Annals of Hilariously Bad Code, Part 2


The problem you run into when deleting large amounts of data is the crappy estimate you get from the table variables.



I've had pretty good luck creating a new version of the proc using temp tables. You could also try just adding recompile hints, but hey, this way we get useful indexes.



As a side note: if you still run into this blocking because this is running long, you can try either removing the transaction code, or changing it to encapsulate each individual delete (though at that point the benefits are negligible).



CREATE   PROCEDURE [dbo].[sp_delete_backuphistory_pro]
@oldest_date datetime
AS
BEGIN
SET NOCOUNT ON

CREATE TABLE #backup_set_id (backup_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #media_set_id (media_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #restore_history_id (restore_history_id INT PRIMARY KEY CLUSTERED)

INSERT INTO #backup_set_id WITH (TABLOCKX) (backup_set_id)
SELECT DISTINCT backup_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #media_set_id WITH (TABLOCKX) (media_set_id)
SELECT DISTINCT media_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #restore_history_id WITH (TABLOCKX) (restore_history_id)
SELECT DISTINCT restore_history_id
FROM msdb.dbo.restorehistory
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)

BEGIN TRANSACTION

DELETE FROM msdb.dbo.backupfile
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupfilegroup
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefile
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefilegroup
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorehistory
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupset
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediafamily
FROM msdb.dbo.backupmediafamily bmf
WHERE bmf.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bmf.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediaset
FROM msdb.dbo.backupmediaset bms
WHERE bms.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bms.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

COMMIT TRANSACTION
RETURN

Quit:
ROLLBACK TRANSACTION

END





share|improve this answer





















  • 1





    +1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

    – marcello miorelli
    11 mins ago











  • @marcellomiorelli 😂

    – Erik Darling
    8 mins ago
















3














My gripes with this proc go back a long way:




  • The Annals of Hilariously Bad Code, Part 1: Critique the Code

  • The Annals of Hilariously Bad Code, Part 2


The problem you run into when deleting large amounts of data is the crappy estimate you get from the table variables.



I've had pretty good luck creating a new version of the proc using temp tables. You could also try just adding recompile hints, but hey, this way we get useful indexes.



As a side note: if you still run into this blocking because this is running long, you can try either removing the transaction code, or changing it to encapsulate each individual delete (though at that point the benefits are negligible).



CREATE   PROCEDURE [dbo].[sp_delete_backuphistory_pro]
@oldest_date datetime
AS
BEGIN
SET NOCOUNT ON

CREATE TABLE #backup_set_id (backup_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #media_set_id (media_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #restore_history_id (restore_history_id INT PRIMARY KEY CLUSTERED)

INSERT INTO #backup_set_id WITH (TABLOCKX) (backup_set_id)
SELECT DISTINCT backup_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #media_set_id WITH (TABLOCKX) (media_set_id)
SELECT DISTINCT media_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #restore_history_id WITH (TABLOCKX) (restore_history_id)
SELECT DISTINCT restore_history_id
FROM msdb.dbo.restorehistory
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)

BEGIN TRANSACTION

DELETE FROM msdb.dbo.backupfile
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupfilegroup
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefile
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefilegroup
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorehistory
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupset
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediafamily
FROM msdb.dbo.backupmediafamily bmf
WHERE bmf.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bmf.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediaset
FROM msdb.dbo.backupmediaset bms
WHERE bms.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bms.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

COMMIT TRANSACTION
RETURN

Quit:
ROLLBACK TRANSACTION

END





share|improve this answer





















  • 1





    +1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

    – marcello miorelli
    11 mins ago











  • @marcellomiorelli 😂

    – Erik Darling
    8 mins ago














3












3








3







My gripes with this proc go back a long way:




  • The Annals of Hilariously Bad Code, Part 1: Critique the Code

  • The Annals of Hilariously Bad Code, Part 2


The problem you run into when deleting large amounts of data is the crappy estimate you get from the table variables.



I've had pretty good luck creating a new version of the proc using temp tables. You could also try just adding recompile hints, but hey, this way we get useful indexes.



As a side note: if you still run into this blocking because this is running long, you can try either removing the transaction code, or changing it to encapsulate each individual delete (though at that point the benefits are negligible).



CREATE   PROCEDURE [dbo].[sp_delete_backuphistory_pro]
@oldest_date datetime
AS
BEGIN
SET NOCOUNT ON

CREATE TABLE #backup_set_id (backup_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #media_set_id (media_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #restore_history_id (restore_history_id INT PRIMARY KEY CLUSTERED)

INSERT INTO #backup_set_id WITH (TABLOCKX) (backup_set_id)
SELECT DISTINCT backup_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #media_set_id WITH (TABLOCKX) (media_set_id)
SELECT DISTINCT media_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #restore_history_id WITH (TABLOCKX) (restore_history_id)
SELECT DISTINCT restore_history_id
FROM msdb.dbo.restorehistory
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)

BEGIN TRANSACTION

DELETE FROM msdb.dbo.backupfile
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupfilegroup
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefile
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefilegroup
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorehistory
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupset
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediafamily
FROM msdb.dbo.backupmediafamily bmf
WHERE bmf.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bmf.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediaset
FROM msdb.dbo.backupmediaset bms
WHERE bms.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bms.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

COMMIT TRANSACTION
RETURN

Quit:
ROLLBACK TRANSACTION

END





share|improve this answer















My gripes with this proc go back a long way:




  • The Annals of Hilariously Bad Code, Part 1: Critique the Code

  • The Annals of Hilariously Bad Code, Part 2


The problem you run into when deleting large amounts of data is the crappy estimate you get from the table variables.



I've had pretty good luck creating a new version of the proc using temp tables. You could also try just adding recompile hints, but hey, this way we get useful indexes.



As a side note: if you still run into this blocking because this is running long, you can try either removing the transaction code, or changing it to encapsulate each individual delete (though at that point the benefits are negligible).



CREATE   PROCEDURE [dbo].[sp_delete_backuphistory_pro]
@oldest_date datetime
AS
BEGIN
SET NOCOUNT ON

CREATE TABLE #backup_set_id (backup_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #media_set_id (media_set_id INT PRIMARY KEY CLUSTERED)
CREATE TABLE #restore_history_id (restore_history_id INT PRIMARY KEY CLUSTERED)

INSERT INTO #backup_set_id WITH (TABLOCKX) (backup_set_id)
SELECT DISTINCT backup_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #media_set_id WITH (TABLOCKX) (media_set_id)
SELECT DISTINCT media_set_id
FROM msdb.dbo.backupset
WHERE backup_finish_date < @oldest_date

INSERT INTO #restore_history_id WITH (TABLOCKX) (restore_history_id)
SELECT DISTINCT restore_history_id
FROM msdb.dbo.restorehistory
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)

BEGIN TRANSACTION

DELETE FROM msdb.dbo.backupfile
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupfilegroup
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefile
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorefilegroup
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.restorehistory
WHERE restore_history_id IN (SELECT restore_history_id
FROM #restore_history_id)
IF (@@error > 0)
GOTO Quit

DELETE FROM msdb.dbo.backupset
WHERE backup_set_id IN (SELECT backup_set_id
FROM #backup_set_id)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediafamily
FROM msdb.dbo.backupmediafamily bmf
WHERE bmf.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bmf.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

DELETE msdb.dbo.backupmediaset
FROM msdb.dbo.backupmediaset bms
WHERE bms.media_set_id IN (SELECT media_set_id
FROM #media_set_id)
AND ((SELECT COUNT(*)
FROM msdb.dbo.backupset
WHERE media_set_id = bms.media_set_id) = 0)
IF (@@error > 0)
GOTO Quit

COMMIT TRANSACTION
RETURN

Quit:
ROLLBACK TRANSACTION

END






share|improve this answer














share|improve this answer



share|improve this answer








edited 4 mins ago

























answered 15 mins ago









Erik DarlingErik Darling

22.2k1269111




22.2k1269111








  • 1





    +1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

    – marcello miorelli
    11 mins ago











  • @marcellomiorelli 😂

    – Erik Darling
    8 mins ago














  • 1





    +1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

    – marcello miorelli
    11 mins ago











  • @marcellomiorelli 😂

    – Erik Darling
    8 mins ago








1




1





+1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

– marcello miorelli
11 mins ago





+1 Now that's my man! Keep training those biceps and improving those procedures! I will accept the answer straight away, I am sure you have done all the testing!

– marcello miorelli
11 mins ago













@marcellomiorelli 😂

– Erik Darling
8 mins ago





@marcellomiorelli 😂

– Erik Darling
8 mins ago













1














Here is something you could try.




  • Restore a backup of your MSDB database to a test server and call it
    something like MSDB_TEST.

  • Once restored, go into the sp_delete_backuphistory stored procedure
    in the MSDB_TEST database and search/replace msdb. with
    msdb_test. and alter it.

  • Capture the current row count of the tables you are interested in.

  • Now, run the altered version of the sp_delete_backuphistory stored procedure in the MSDB_TEST database.

  • Compare the current row counts to the previously capture ones.






share|improve this answer
























  • +1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

    – marcello miorelli
    32 mins ago








  • 1





    @marcellomiorelli - understood - I'm afraid that's all I have for this problem.

    – Scott Hodgin
    28 mins ago
















1














Here is something you could try.




  • Restore a backup of your MSDB database to a test server and call it
    something like MSDB_TEST.

  • Once restored, go into the sp_delete_backuphistory stored procedure
    in the MSDB_TEST database and search/replace msdb. with
    msdb_test. and alter it.

  • Capture the current row count of the tables you are interested in.

  • Now, run the altered version of the sp_delete_backuphistory stored procedure in the MSDB_TEST database.

  • Compare the current row counts to the previously capture ones.






share|improve this answer
























  • +1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

    – marcello miorelli
    32 mins ago








  • 1





    @marcellomiorelli - understood - I'm afraid that's all I have for this problem.

    – Scott Hodgin
    28 mins ago














1












1








1







Here is something you could try.




  • Restore a backup of your MSDB database to a test server and call it
    something like MSDB_TEST.

  • Once restored, go into the sp_delete_backuphistory stored procedure
    in the MSDB_TEST database and search/replace msdb. with
    msdb_test. and alter it.

  • Capture the current row count of the tables you are interested in.

  • Now, run the altered version of the sp_delete_backuphistory stored procedure in the MSDB_TEST database.

  • Compare the current row counts to the previously capture ones.






share|improve this answer













Here is something you could try.




  • Restore a backup of your MSDB database to a test server and call it
    something like MSDB_TEST.

  • Once restored, go into the sp_delete_backuphistory stored procedure
    in the MSDB_TEST database and search/replace msdb. with
    msdb_test. and alter it.

  • Capture the current row count of the tables you are interested in.

  • Now, run the altered version of the sp_delete_backuphistory stored procedure in the MSDB_TEST database.

  • Compare the current row counts to the previously capture ones.







share|improve this answer












share|improve this answer



share|improve this answer










answered 51 mins ago









Scott HodginScott Hodgin

17.9k21634




17.9k21634













  • +1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

    – marcello miorelli
    32 mins ago








  • 1





    @marcellomiorelli - understood - I'm afraid that's all I have for this problem.

    – Scott Hodgin
    28 mins ago



















  • +1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

    – marcello miorelli
    32 mins ago








  • 1





    @marcellomiorelli - understood - I'm afraid that's all I have for this problem.

    – Scott Hodgin
    28 mins ago

















+1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

– marcello miorelli
32 mins ago







+1 for always being helpful - Yes that could be a way - one that I was trying to avoid to be honest

– marcello miorelli
32 mins ago






1




1





@marcellomiorelli - understood - I'm afraid that's all I have for this problem.

– Scott Hodgin
28 mins ago





@marcellomiorelli - understood - I'm afraid that's all I have for this problem.

– Scott Hodgin
28 mins ago


















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233375%2fhow-to-minimize-plan-ahead-the-effect-of-running-sp-delete-backuphistory-measur%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Færeyskur hestur Heimild | Tengill | Tilvísanir | LeiðsagnarvalRossið - síða um færeyska hrossið á færeyskuGott ár hjá færeyska hestinum

He _____ here since 1970 . Answer needed [closed]What does “since he was so high” mean?Meaning of “catch birds for”?How do I ensure “since” takes the meaning I want?“Who cares here” meaningWhat does “right round toward” mean?the time tense (had now been detected)What does the phrase “ring around the roses” mean here?Correct usage of “visited upon”Meaning of “foiled rail sabotage bid”It was the third time I had gone to Rome or It is the third time I had been to Rome

Bunad