tstaker (3/3/2010)
Great Article Wayne! Thanks!"Then, verify your backup – until you do so, you don’t know if it’s good or not. In case you manage to really mess up the database, you can restore from this backup and start over (or, preferably, proceed with copying the data to a new database)."
This is a great point. Normally when I work with corruption, If possible, I'll restore the database to a test server and go through all the troubleshooting there. If I mess up I've only destroyed a copy of the database and not the production database. Sometimes I'll go through corrective steps 2 or 3 times and document it before I fix the live database.
Now that is a great idea! Granted that you can't always do this for all types of corruption, but for what this article is about that would definitely be a smarter way to do it.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes