ken.trock (1/4/2010)
Speak of Murphy and he will appear. Right here is a good example. No backups. Corrupt file. Just the same as flat tire, no spare.
This is something of a sad story. Hope it works out.
I've read a lot where the final step in a backup process is to ensure you can actually restore the backup :-D. We update our hardware frequently enough such that we do side by side updates (sometimes upgrading the SQL version too) where we restore last night's backups onto our new servers. Proof positive:exclamation:
Ken
Exactly. And you have a reasonable assurance that you'll be able to do a restore and that it will work in a real emergency. That's the way it should be.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning