Get-DbaSuspectPage

Want to see the source code for this command? Check out Get-DbaSuspectPage on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbaSuspectPage.

Synopsis

Returns data that is stored in SQL for Suspect Pages on the specified SQL Server Instance

Description

This function returns any records that were stored due to suspect pages in databases on a SQL Server Instance.

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

The database to return. If unspecified, all records will be returned.

-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.