Skip to content

Latest commit

 

History

History
83 lines (51 loc) · 5.13 KB

configure-predefined-replication-alerts-sql-server-management-studio.md

File metadata and controls

83 lines (51 loc) · 5.13 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic ms.custom helpviewer_keywords monikerRange
Configure predefined Replication alerts (SSMS)
Learn how to configure predefined replication alerts using SQL Server Management Studio (SSMS).
MashaMSFT
mathoma
09/25/2024
sql
replication
how-to
updatefrequency5
alerts [SQL Server replication]
predefined replication alerts [SQL Server replication]
=azuresqldb-mi-current||>=sql-server-2016

Configure Predefined Replication Alerts (SQL Server Management Studio)

[!INCLUDEapplies-to-version/_ssnoversion.md] Replication offers the following predefined alerts, which can be configured to respond to replication events:

  • Replication: agent success

  • Replication: agent failure

  • Replication: agent retry

  • Replication: expired subscription dropped

  • Replication: Subscription reinitialized after validation failure

  • Replication: Subscriber has failed data validation

  • Replication: Subscriber has passed data validation

  • Replication: agent custom shutdown

Configure these alerts from the Alerts folder in [!INCLUDEmsCoName] [!INCLUDEssManStudioFull] or the Warnings tab in Replication Monitor. For more information about accessing this tab, see View information and perform tasks using Replication Monitor.

In addition to these alerts, Replication Monitor provides a set of warnings and alerts related to status and performance. For more information, see Set Thresholds and Warnings in Replication Monitor. You can also define alerts for other replication events using the [!INCLUDEssNoVersion] alerts infrastructure. For more information, see Create a User-Defined Event.

To configure a predefined replication alert in Management Studio

  1. Connect to the Distributor in [!INCLUDEssManStudio], and then expand the server node.

  2. Expand the SQL Server Agent folder, and then expand the Alerts folder.

  3. Right-click a replication alert, and then click Properties.

  4. Set options in the <AlertName> alert properties dialog box:

    • On the General page, click Enable; specify which database the alert should apply to.

    • On the Response page, specify whether an e-mail should be sent and/or a job should be executed.

      If the alert is Replication: Subscriber has failed data validation, you can specify the response job that replication provides for this alert: Select Execute job, and then click the browse button (...). In the Locate Job dialog box, click Browse. In the Browse for Objects dialog box, select Reinitialize subscriptions having data validation failures. Click OK in both open dialog boxes. When the job executes, it uses a remote procedure call (RPC) to a stored procedure that reinitializes the subscription. If the Publisher uses a remote Distributor, you must define a remote server login at the Publisher, so that the RPC from the Distributor to the Publisher can be made.

    • On the Options page, customize the text of the response.

  5. Select OK.

To configure an alert for a threshold in Replication Monitor

  1. On the Warnings tab click Configure Alerts.

  2. In the Configure Replication Alerts dialog box, select an alert, and then click Configure.

  3. Set options in the <AlertName> alert properties dialog box:

    • On the General page, click Enable; specify which database the alert should apply to.

    • On the Response page, specify whether an e-mail should be sent and/or a job should be executed.

      If the alert is Replication: Subscriber has failed data validation, you can specify the response job that replication provides for this alert: Select Execute job, and then click the browse button (...). In the Locate Job dialog box, click Browse. In the Browse for Objects dialog box, select Reinitialize subscriptions having data validation failures. Click OK in both open dialog boxes. When the job executes, it uses a remote procedure call (RPC) to a stored procedure that reinitializes the subscription. If the Publisher uses a remote Distributor, you must define a remote server login at the Publisher, so that the RPC from the Distributor to the Publisher can be made.

    • On the Options page, customize the text of the response.

  4. Select OK.

  5. Click Close.

Related content