So often I get the call from someone needing help with repairing a corrupt database, and then they tell me that they ran CHECKDB with REPAIR_ALLOW_DATA_LOSS and at that point I realize it is going to be more difficult to get all their data back and repaired. When working with CheckDB and SQL Server, whether you are on SQL Server …
When running DBCC CHECKDB, you will often times get screens of information back stating that the database is all okay, and that it checked every table. This can be quite tedious when you are trying to search through thousands of lines of output to see where the real error is. You can use the WITH NO_INFOMSGS when running checkdb to …
Recently we had a new customer contact from someone with a corrupt database. They were getting corruption error #824, which usually indicates there is some type of corruption in the database. Every time they ran a backup of the database there was an error #824 thrown into the SQL log and into the job failure message. When running CheckDB the …
In 2015, around the time I started Stedman Solutions LLC, I created the Database Corruption Challenge as a way to share knowledge of how to repair corrupt databases and to provide options to running REPAIR_ALLOW_DATA_LOSS. Today the lessons from the corruption challenge are just as valid as they were in 2015, it is a good place to start if you …
When working with clients on fixing their corrupt SQL Server databases we run into some common beliefs about corruption that are not quite true, such as: A full backup and restore of a corrupt database may help fix the corruption. This is FALSE. If the database is not so corrupt that backups are failing, the full back up a database, …
I received a contact message from the “Contact us” form, asking about how to go about repairing corruption in TempDB. The error message was something like this: SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:118576; actual 0:0). It occurred during a read of page (1:118576) in database ID 2 at offset 0xxxxxxx in file ‘xxxxx\tempdb.mdf’. Additional …
At Stedman Solutions, LLC, we recently had the opportunity to help out another client with a corrupt database, to completely recover all their data and remove all the corruption. In this specific scenario Microsoft had told them that their only options was to restore from a backup, but because the corruption had been there for a while before they noticed …
Please join me on Saturday March 16 in Victoria BC Canada for my SQL Saturday presentation on the Basics of Database Corruption Repair. Here is the session, the Basics of Database Corruption Repair. Duration: 60 minutesTrack: AdminLevel: Intermediate Your database is running fine month after month with no problems. Suddenly someone reports that their query won’t run. They get an …
Recently Derrick and I had a chance to help with a corruption repair in Thailand, just to clarify, the client was in Thailand, not us. This was our second corruption of the year this year. Here is what the client had to say when we were done helping. We were in a bind, our clients are a manufacturing facility with …
I discovered this recording from a Database corruption repair presentation that I did a few years ago: Related Links Corruption Repair by Stedman Solutions Corruption Challenge