It was a busy week this week, but I was able to create several blog posts relating to corruption. Does a corrupt database really need to be repaired?June 11, 2020 At Stedman Solutions, LLC the team and I do many database …
At Stedman Solutions, LLC the team and I do many database repairs from simple things that take just a few minutes to larger repairs that take many days to repair. Since 2015 we have been doing database corruption repair and …
Does a corrupt database really need to be repaired? Read more »
First rules about a database being in suspect mode: A SQL database that is SUSPECT implies that it was unable to completely start up after a shutdown. For instance, if the power was unplugged from the SQL Server while shutting …
What does it mean when a SQL Database is SUSPECT? Read more »
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 …
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 …
One of the common CheckDB errors that I see is the Message 824, level 24. This is something that I regularly work to repair for customers with great success. DBCC results for ‘YourDatabaseName’. CHECKDB found 0 allocation errors and …
The REPAIR_ALLOW_DATA_LOSS option for DBCC CHECKDB and DBCC CHECKTABLE can be one of the most misleading and possibly catastrophic options. What the REPAIR_ALLOW_DATA_LOSS option does for DBCC CHECKDB and DBCC CHECKTABLE is to simply just throw away any pages (8k …
Database Corruption Overview: Database corruption is one of those things that you can only plan for by practicing your response plan. Out of all of the things that can happen to your SQL Server this is the one that you …
Database corruption repair with SQL Server is one of those things that you generally don’t see every day, but as a DBA, you are expected to be able to fix it quickly without any data loss. From the risk analysis …
Database Corruption Challenge #9 has completed with 19 winning participants, you can take a look at the scoring page for exact details. The first to solve the challenge this week was Eduardo Rezende who provided the winning solution just 58 minutes …