Skip to content

check-integrity-of-database-with-suspect-pages.md

Latest commit

 

History

History
33 lines (25 loc) · 1.77 KB

check-integrity-of-database-with-suspect-pages.md

File metadata and controls

33 lines (25 loc) · 1.77 KB
title Check Integrity of Database with Suspect Pages | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service database-engine
ms.reviewer
ms.technology security
ms.topic conceptual
helpviewer_keywords
Best Practices [Database Engine]
ms.assetid 3b1ec9fe-f6c5-46f7-aa63-6e671be1572d
author VanMSFT
ms.author vanto

Check Integrity of Database with Suspect Pages

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This rule checks for user databases that have the database status set to suspect. When the [!INCLUDEssDEnoversion] reads a database page that contains an 824 error, the page is considered suspect, its page ID is recorded in the suspect_pages table in msdb, and the database that contains the page is set to suspect.

Error 824 indicates that a logical consistency error was detected during a read operation. This error frequently indicates data corruption caused by a faulty I/O subsystem component. This is a severe error condition that threatens database integrity and must be corrected immediately.

Best Practices Recommendations

  • Review the [!INCLUDEssNoVersion] error log for the details of the 824 error for this database.

  • Complete a full database consistency check (DBCC CHECKDB).

  • Implement the user actions that are defined in MSSQLSERVER_824.

For More Information

Manage the suspect_pages Table (SQL Server)