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 …
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 …
Part of good server monitoring it to have alerts enabled for a number of different errors to know when things go bad. The problem is we were getting the following error every time the server was restarted. SQL Server Alert System: ‘ERROR 824’ occurred on \\MyServerNameDESCRIPTION: SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xe660dd36; actual: 0xcd481907). …
Earlier today I had the opportunity to release the September update of Database Health Monitor. This is version 2.91. One of the updates is a new feature called aliasing, where you can add a tag to the name of the server in the tree view on the left hand side as shown in the picture below. The first database in …
Today I released the August 2019 release of Database Health Monitor. This is version 2.9. My favorite new report is the Blocking By Hour of Day report which uses the existing data that is collected by the historic monitoring feature. Below is a list of some of the things that have been fixed or added in this version and the …
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 …
Yesterday I released the first update to Database Health Monitor in a couple of months. There were some new features and some fixed saved up that were released yesterday. I did however run into 2 small bugs that were quickly dealt with in version 2.8.0 and 2.8.1. With some quick bug reporting for a couple of super users, and some …
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 blocks of data) that contain rows. This may mean it is throwing away a couple of rows, or dozens to …
In a perfect world, your SQL Server would be so secure that you would not need antivirus software, you would have behind layers of firewalls, nobody would ever connect with remote desktop to install anything, and it would always have all of the latest security patches… But that is not the real world. Given that your SQL Server often times …