---
title: "Database Suspect Data Page Event Class | Microsoft Docs"
ms.custom: ""
ms.date: "03/15/2017"
ms.prod: sql
ms.reviewer: ""
ms.technology: supportability
ms.topic: conceptual
helpviewer_keywords: 
  - "event notifications [SQL Server], database mirroring"
  - "suspect_pages system table"
  - "database mirroring [SQL Server], event notifications"
  - "Database Suspect Data Page event class"
ms.assetid: 098e1443-a8a0-425c-9311-0a479b1370ed
author: "stevestein"
ms.author: "sstein"
monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current"
---
# Database Suspect Data Page Event Class
[!INCLUDE[appliesto-ss-asdb-xxxx-xxx-md](../../includes/appliesto-ss-asdb-xxxx-xxx-md.md)]
  The **Database Suspect Data Page** event class indicates when a page is added to the [suspect_pages](../../relational-databases/system-tables/suspect-pages-transact-sql.md) table in [msdb](../../relational-databases/databases/msdb-database.md). Include this event class in traces that are monitoring the occurrence of suspect pages.  
  
> [!NOTE]  
>  This event is issued asynchronously from the insertion of a corresponding row into the **suspect_pages** table. Therefore, a job listening on this event might not find the corresponding **suspect_pages** entry immediately.  
  
 When the **Database Suspect Data Page** event class is included in a trace the relative overhead is low. The overhead might be greater if the number of suspect pages increases, for example, if a disk drive is experiencing problems.  
  
## Database Suspect Data Page Event Class Data Columns  
  
|Data Column Name|Data Type|Description|Column ID|Filterable|  
|----------------------|---------------|-----------------|---------------|----------------|  
|**DatabaseID**|**int**|ID of the database for which the suspect page event has been raised. This is the same as the **database_id** column of the **suspect_pages** table.|3|Yes|  
|**EventClass**|**int**|The type of the event is 213.|27|No|  
|**EventSequence**|**int**|Sequence of event class in batch.|51|No|  
|**SPID**|**int**|ID of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] task that encountered the suspect page.|12|Yes|  
|**StartTime**|**datetime**|Time that the event occurred.|14|Yes|  
|**ObjectID**|**int**|ID of the database file that contains the suspect page. This is the same as the **file_id** column of the **suspect_pages** table.|22|Yes|  
|**ObjectID2**|**int**|ID of the suspect page in the file. This is the same as the **page_id** column of the **suspect_pages** table.|56|Yes|  
|**Error**|**int**|Type of error that was encountered . This value is the same as the **event_type** value for the page in the **suspect_pages** table.|31|Yes|  
  
## See Also  
 [sp_trace_setevent (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-trace-setevent-transact-sql.md)   
 [Manage the suspect_pages Table (SQL Server)](../../relational-databases/backup-restore/manage-the-suspect-pages-table-sql-server.md)