SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Wayne Sheffield / Fixing DBCC CHECKDB Msg 8992 Errors / Latest Posts

RE: Fixing DBCC CHECKDB Msg 8992 Errors

WayneS — Wed, 03 Mar 2010 14:29:14 GMT

Tom, Brad, "tstaker", Randy and Jason: I'm glad you'll liked the article... and I hope you never need to reference it!@Jason: plus, you get a point for doing so. ;-)

RE: Fixing DBCC CHECKDB Msg 8992 Errors

SQLRNNR — Wed, 03 Mar 2010 12:51:00 GMT

Nice article Wayne. I've told you that already - but now it is posted with the article too :-D

RE: Fixing DBCC CHECKDB Msg 8992 Errors

Randy Rabin — Wed, 03 Mar 2010 10:22:37 GMT

Great article! Just wanted to add that in addition to (sometimes in lieu of) taking a backup of the database before "experimenting", I often shut down SQL and make a physical filecopy of the MDF/NDF/LDF files. If something goes wrong, just move the copied files back overtop of the originals and you're back in business.Yet another reason to make sure you back up everything *before* upgrading SQL -- even for a service pack install.

RE: Fixing DBCC CHECKDB Msg 8992 Errors

WayneS — Wed, 03 Mar 2010 09:36:12 GMT

[quote][b]tstaker (3/3/2010)[/b][hr]Great Article Wayne! Thanks!"[i]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).[/i]"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.[/quote]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.

RE: Fixing DBCC CHECKDB Msg 8992 Errors

Trey Staker — Wed, 03 Mar 2010 08:15:47 GMT

Great Article Wayne! Thanks!"[i]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).[/i]"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.

RE: Fixing DBCC CHECKDB Msg 8992 Errors

SQLBalls — Wed, 03 Mar 2010 07:43:41 GMT

Hey Wayne, Great article, I was wondering what the resolution to the problem you guys encountered was. I've really enjoyed reading Paul's blog as well he has a lot of great info.

RE: Fixing DBCC CHECKDB Msg 8992 Errors

Tom Garth — Wed, 03 Mar 2010 07:41:25 GMT

Thanks Wayne. That's good information.

Fixing DBCC CHECKDB Msg 8992 Errors

WayneS — Tue, 02 Mar 2010 21:11:32 GMT

Comments posted to this topic are about the item [B]Fixing DBCC CHECKDB Msg 8992 Errors[/B]