An effective backup needs a tested restore plan as well as a schedule. I keep these seven reminders in recovery discussions.
What does Keyword STATS Indicates in Backup Scripts in SQL Server? – Interview Question of the Week #138
Many DBAs add STATS to their Backup Scripts without knowing why. It prints percent complete messages while the backup runs. Here is how it works.
SQL SERVER – Msg 1833 – File Cannot be Reused Until After the Next BACKUP LOG Operation
Adding a file during a demo failed with Msg 1833: file cannot be reused until after the next BACKUP LOG operation. Here is the root cause.
What does BACKUP WITH NAME Command do? – Interview Question of the Week #130
What does BACKUP WITH NAME do? It simply names your backup, and you can then find that name in the msdb backupset table. Here is a quick example.
Log Shipping Alternative for Databases in Simple Recovery Model
A log shipping alternative for a database in the simple recovery model is a second copy that restores the newest full backup and the newest differential backup. This post finds those two files from the backup history in msdb, restores them with MOVE and RECOVERY, and repeats the cycle on a schedule. It also states what you lose compared with real log shipping.
SQL SERVER – FIX: Msg 3009, Level 16 – Could not Insert a Backup or Restore History Detail Record in the msdb Database
A slow restore that my client cancelled led to Msg 3009: could not insert a backup or restore history record in msdb. Here is what I learned about a trace flag.
What is Copy Only Backup in SQL Server? – Interview Question of the Week #128
Copy Only Backup is an independent backup that does not break the LSN chain or disturb your regular backup plan. Here is the short answer and a longer one.