Validate SQL Server Backups Exist with Policy Based Management

I recently submitted a tip regarding the existence of your backup files using the undocumented system stored procedure xp_fileexist. But how would you go about executing that script against all your SQL Server 2005 and SQL Server 2008 instances? I took that script and decided to go one step further using Policy Based Management to create a custom policy that you can then run against all your SQL Server 2005 and SQL Server 2008 instances.

SQL Backup 6: Wind of Change

One could be forgiven for thinking that there's little more you can do with third-party backup software than just ...er... backup databases. Shawn McGehee gives us his personal take on the implications of the improvements that have been made to SQL Backup for version 6.

How SQL Server recovery models impact your SharePoint ...

SharePoint administrators can minimize data loss by selecting the appropriate SQL Server recovery model. But which model is right for your enterprise?

BACKUP / RESTORE

Backup and Restore Tables

Truncating the log

Script to check that backup files still exist for SQL Server

You have configured your database backup jobs without any problems. The backups themselves seem to be working, but are the files still where you think they are? How do you know they have not been moved, or worse, deleted to free up some space on your server? And when would you find out that the files were no longer there?

Backup Both Full and TLog Database Backup within a single Job

This script is basically used in SQL Server 2005/2008 as that version not having the option to perform the same activity in the single window.

Restore Database from network location

When using GUI tools, it seems the DB cannot be restored from a network path. This is actually possible via the script.

Copy Only Backup for SQL 2005 and SQL 2008

Is there any way that my ad hoc backups will not interrupt the sequence of my backup plan?