Get-DbaSuspectPage

Synopsis

Retrieves suspect page records from msdb database for corruption detection and analysis

Description

Queries the msdb.dbo.suspect_pages table to identify database pages that have experienced corruption events such as checksum failures, torn pages, or I/O errors. SQL Server automatically logs corrupt pages to this system table when encountered during read operations, making this function essential for proactive corruption monitoring and troubleshooting. Returns detailed information including the specific database, file, page location, error type, occurrence count, and last detection date to help DBAs prioritize remediation efforts.

Syntax

Get-DbaSuspectPage
    [-SqlInstance] <DbaInstanceParameter[]>
    [[-Database] <Object>]
    [[-SqlCredential] <PSCredential>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Get-DbaSuspectPage -SqlInstance sql2016

Retrieve any records stored for Suspect Pages on the sql2016 SQL Server.

Example: 2

PS C:\> Get-DbaSuspectPage -SqlInstance sql2016 -Database Test

Retrieve any records stored for Suspect Pages on the sql2016 SQL Server and the Test database only.

Required Parameters

-SqlInstance

The target SQL Server instance or instances

Optional Parameters

-Database

Filters suspect page results to a specific database name. When omitted, returns suspect pages from all databases on the instance.
Use this when investigating corruption issues in a particular database or when you need to focus troubleshooting efforts on a single database.

-SqlCredential

Login to the target instance using alternative credentials. Accepts PowerShell credentials (Get-Credential).
Windows Authentication, SQL Server Authentication, Active Directory - Password, and Active Directory - Integrated are all supported.
For MFA support, please use Connect-DbaInstance.

-EnableException

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with “sea of red” exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this “nice by default” feature off and enables you to catch exceptions with your own try/catch.