Set-DbaAgentAlert

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

Synopsis

Modifies properties of existing SQL Agent alerts including enabled status and name.

Description

Modifies existing SQL Agent alerts on one or more SQL Server instances, allowing you to enable, disable, or rename alerts without using SQL Server Management Studio. This function is particularly useful for bulk operations across multiple servers, standardizing alert configurations between environments, or temporarily disabling noisy alerts during maintenance windows. The function works with the JobServer.Alerts collection and uses the SMO Alter() method to commit changes to existing alerts. You can specify alerts by name or pipe in alert objects from other dbatools commands like Get-DbaAgentAlert.

Syntax

Set-DbaAgentAlert
    [[-SqlInstance] <DbaInstanceParameter[]>]
    [[-SqlCredential] <PSCredential>]
    [[-Alert] <Object[]>]
    [[-NewName] <String>]
    [-Enabled]
    [-Disabled]
    [-Force]
    [[-InputObject] <Alert[]>]
    [-EnableException]
    [-WhatIf]
    [-Confirm]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Set-DbaAgentAlert -SqlInstance sql1 -Alert 'Severity 025: Fatal Error' -Disabled

Changes the alert to disabled.

Example: 2

PS C:\> Set-DbaAgentAlert -SqlInstance sql1 -Alert 'Severity 025: Fatal Error', 'Error Number 825', 'Error Number 824' -Enabled

Changes multiple alerts to enabled.

Example: 3

PS C:\> Set-DbaAgentAlert -SqlInstance sql1, sql2, sql3 -Alert 'Severity 025: Fatal Error', 'Error Number 825', 'Error Number 824' -Enabled

Changes multiple alerts to enabled on multiple servers.

Example: 4

PS C:\> Set-DbaAgentAlert -SqlInstance sql1 -Alert 'Severity 025: Fatal Error' -Disabled -WhatIf

Doesn't Change the alert but shows what would happen.

Optional Parameters

-SqlInstance

The target SQL Server instance or instances. You must have sysadmin access and server version must be SQL Server version 2000 or greater.

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

-Alert

Specifies the name(s) of the SQL Agent alerts to modify. Accepts multiple alert names for bulk operations.
Use this when you need to update specific alerts by name across one or more instances.

-NewName

Sets a new name for the alert being modified. Only works when modifying a single alert.
Use this when standardizing alert names across environments or fixing naming conventions.

-Enabled

Enables the specified SQL Agent alert(s) by setting IsEnabled to true.
Use this to reactivate alerts after maintenance or to ensure critical alerts are active across all instances.

-Disabled

Disables the specified SQL Agent alert(s) by setting IsEnabled to false.
Use this during maintenance windows or to silence noisy alerts that are firing incorrectly.

-Force

Bypasses confirmation prompts by setting ConfirmPreference to 'none'.
Use this in automated scripts where you want to suppress interactive prompts.

-InputObject

Accepts SQL Agent alert objects from the pipeline, typically from Get-DbaAgentAlert.
Use this when you want to filter alerts first, then modify the results in a pipeline operation.

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

-WhatIf

Shows what would happen if the command were to run. No actions are actually performed.

-Confirm

Prompts you for confirmation before executing any changing operations within the command.