Copy-DbaAgentAlert

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

Synopsis

Copies SQL Server Agent alerts from source instance to destination instances

Description

Transfers SQL Server Agent alerts from a source instance to one or more destination instances, preserving their configurations, notification settings, and job associations. This function handles the complex dependencies between alerts, operators, and jobs automatically, ensuring alerts work properly after migration.

Essential for server migrations, disaster recovery preparation, and standardizing monitoring across multiple SQL Server environments. Prevents manual recreation of dozens of alerts and their intricate notification chains.

By default, all alerts are copied, but you can specify individual alerts with the -Alert parameter. Existing alerts are skipped unless -Force is used to overwrite them.

Syntax

Copy-DbaAgentAlert
    [-Source] <DbaInstanceParameter>
    [[-SourceSqlCredential] <PSCredential>]
    [-Destination] <DbaInstanceParameter[]>
    [[-DestinationSqlCredential] <PSCredential>]
    [[-Alert] <Object[]>]
    [[-ExcludeAlert] <Object[]>]
    [-IncludeDefaults]
    [-Force]
    [-EnableException]
    [-WhatIf]
    [-Confirm]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Copy-DbaAgentAlert -Source sqlserver2014a -Destination sqlcluster

Copies all alerts from sqlserver2014a to sqlcluster using Windows credentials. If alerts with the same name exist on sqlcluster, they will be skipped.

Example: 2

PS C:\> Copy-DbaAgentAlert -Source sqlserver2014a -Destination sqlcluster -Alert PSAlert -SourceSqlCredential $cred -Force

Copies a only the alert named PSAlert from sqlserver2014a to sqlcluster using SQL credentials for sqlserver2014a and Windows credentials for sqlcluster. If an alert with the same name exists on
sqlcluster, it will be dropped and recreated because -Force was used.

Example: 3

PS C:\> Copy-DbaAgentAlert -Source sqlserver2014a -Destination sqlcluster -WhatIf -Force

Shows what would happen if the command were executed using force.

Required Parameters

-Source

Specifies the source SQL Server instance containing the alerts to copy. Must be SQL Server 2000 or higher.
Use this to identify the server with the alert configurations you want to migrate or replicate.

-Destination

Specifies one or more destination SQL Server instances where alerts will be copied. Must be SQL Server 2000 or higher.
Accepts multiple instances to copy alerts to several servers simultaneously during migrations or standardization efforts.

Optional Parameters

-SourceSqlCredential

Specifies alternative credentials for connecting to the source SQL Server instance.
Use this when the current Windows credentials don't have access to the source server or when connecting with SQL Server authentication.

-DestinationSqlCredential

Specifies alternative credentials for connecting to the destination SQL Server instances.
Use this when the current Windows credentials don't have access to destination servers or when connecting with SQL Server authentication.

-Alert

Specifies specific alert names to copy instead of copying all alerts from the source instance.
Use this when you only need to migrate particular alerts rather than the entire alert configuration.

-ExcludeAlert

Specifies alert names to skip during the copy operation while processing all other alerts.
Use this when you want to copy most alerts but exclude specific ones that shouldn't be migrated.

-IncludeDefaults

Copies SQL Server Agent system settings including FailSafeEmailAddress, ForwardingServer, and PagerSubjectTemplate.
Use this when migrating to a new server where you want to replicate the source server's Agent notification configuration.

-Force

Drops and recreates alerts that already exist on the destination servers instead of skipping them.
Use this when you need to overwrite existing alerts with updated configurations from the source.

-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

If this switch is enabled, no actions are performed but informational messages will be displayed that explain what would happen if the command were to run.

-Confirm

If this switch is enabled, you will be prompted for confirmation before executing any operations that change state.