What part of the SQLDump suggest database corruption? A reader asked, and I show the DbccResults tag in the SQLDump text file that confirms it.
DBCC CHECKDB Running Slow? Check the MAXDOP Option
DBCC CHECKDB running slow can trace back to the MAXDOP option. A CHECKDB with no MAXDOP option uses the server’s max degree of parallelism, and one with its own option overrides it. This post times CHECKDB on a 2 GB database with four settings, adds PHYSICAL_ONLY, and lists the other causes to rule out.
Splitting DBCC CHECKDB Across the Week for a Large Database
Keep a large database under regular integrity checks by splitting DBCC CHECKDB work across seven nights and auditing coverage.
Error 5511: FILESTREAM File System Log Record Is Corrupted
Error 5511 kept a production database offline after a SQL Server restart, because a FILESTREAM log record under the log folder was corrupted. We moved the corrupted file to another folder and the database came online. CHECKDB came out clean and the client saw no problems for weeks.
SQL SERVER – Database Attach Failure – Msg 2571 – User ‘guest’ Does Not Have Permission to Run DBCC Checkprimaryfile.
Attaching MDF and LDF files after a disaster failed with Msg 2571: user guest does not have permission to run DBCC checkprimaryfile. Here is the fix.
CPerIndexMetaQS::ErrorAbort: Too Many Dumps From Index Corruption
CPerIndexMetaQS::ErrorAbort in a stack dump points to index corruption in one of your databases. A reader had too many dumps, and the ERRORLOG and DBCC CHECKTABLE showed which index was bad. Here are the two repair options and why backups matter.
SQL SERVER – Msg 0, Level 11 – A Severe Error Occurred on the Current Command. The results, if Any, Should be Discarded
Msg 0, Level 11 says a severe error occurred but gives no clue how to fix it. Here is my checklist, starting with DBCC CHECKDB on the database and table.