List of Backups is too big

I have a Maintenance Plan which runs Backup of DB every hour. Backups older
than 2 weeks are deleted automatically. If I check the contents of the
folder containing Backup files then I do not see there those old files which
had to be deleted. They were really deleted. But if I select Restore
Database in EM then I get the list of all files, including deleted ones.
I noticed that the list of Backup files is delivered with bigger and bigger
delay. Maybe I'm wrong but I think it's because of the size of that list.
I'm working with remote Database through VPN connection and I would like to
find the way to make the list of Backup files contain only existing files.
Thank you
Al
That is because each time you backup using the SQL Server Backup command(or
thru the wizard) a row is added to the backup history tables. These rows
are never deleted automatically. You must set up a job or manually run
sp_delete_backuphistory on a regular basis to cap the number of rows in the
history tables. Be aware that the first time you run it the response will
be slow if there are lots of rows in the tables. Once you get it down to a
reasonable size it works just fine.
Andrew J. Kelly SQL MVP
"vul" <aaa@.optonline.net> wrote in message
news:u2m0hnh1EHA.3588@.TK2MSFTNGP14.phx.gbl...
>I have a Maintenance Plan which runs Backup of DB every hour. Backups older
> than 2 weeks are deleted automatically. If I check the contents of the
> folder containing Backup files then I do not see there those old files
> which
> had to be deleted. They were really deleted. But if I select Restore
> Database in EM then I get the list of all files, including deleted ones.
> I noticed that the list of Backup files is delivered with bigger and
> bigger
> delay. Maybe I'm wrong but I think it's because of the size of that list.
> I'm working with remote Database through VPN connection and I would like
> to
> find the way to make the list of Backup files contain only existing files.
> Thank you
> Al
>
|||Thank you very much, Andrew
Al
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:#JxGC9h1EHA.1860@.TK2MSFTNGP15.phx.gbl...
> That is because each time you backup using the SQL Server Backup
command(or
> thru the wizard) a row is added to the backup history tables. These rows
> are never deleted automatically. You must set up a job or manually run
> sp_delete_backuphistory on a regular basis to cap the number of rows in
the
> history tables. Be aware that the first time you run it the response will
> be slow if there are lots of rows in the tables. Once you get it down to
a[vbcol=seagreen]
> reasonable size it works just fine.
>
> --
> Andrew J. Kelly SQL MVP
>
> "vul" <aaa@.optonline.net> wrote in message
> news:u2m0hnh1EHA.3588@.TK2MSFTNGP14.phx.gbl...
older[vbcol=seagreen]
list.[vbcol=seagreen]
files.
>