Now is your chance to ask a question about corruption in SQL Server databases. We will do our best job of answering those questions on our February webcast on database corruption. Do you have a question about the output from DBCC CheckDB? Seeing a strange error in your SQL Server logs? Is your SQL Server sending alerts related to corruption? …
Babelfish for Aurora PostgreSQLDecember 1, 2020Amazon goes after Microsoft’s SQL Server with Babelfish for Aurora PostgreSQL. What is interesting is that a direct port of SQL Server to PostgreSQL or Aurora PostgreSQL can be challenging due to incompatibilities …Babelfish for Aurora PostgreSQLRead More » Sales To Aggressive?November 19, 2020When does a salesperson become too aggressive? In my business I try …
At the beginning of June I realized that I was slightly behind on my blogging, so today, June 30th marks 30 days of 30 blog posts in the month of June. Some other big blogging months were March 2015 and April 2015, around the Database Corruption Challenge, and June 2013 with 27 posts, and May 2013 with 27 posts. I …
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 repairs from simple things that take just a few minutes to larger repairs that take many days to repair. Since …
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 down with open transactions that are currently being written to disk. Causes: The most important thing to do is to …
What does it mean when a SQL Database is SUSPECT? Read more »
Yesterday I posted about how repair_allow_data_loss should never be used with CHECKDB or CHECKTABLE. Today I want to share the difference between repair_rebuild vs repair_allow_data_loss. First off, after reading the post about never using repair_allow_data_loss, and you will understand that repair_allow_data_loss simply throws away pages. Next what repair_rebuild attempts to do is to rebuild pages in non-clustered indexes that are …
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 …
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). …
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 …
One of those services that I offer is on call help for DBA’s who encounter database corruption. Call me anytime 24/7 and as long as you are an existing customer, or we can work out a billing arrangement to turn you into a paying customer, I can help. That’s all a good if you are familiar with what database …