StarQuest Technical Documents

How to Configure a Notification Alert for an SQDR Replication Event

Last Update: 07 February 2005
Product: StarQuest Data Replicator
Version: 3.x
Article ID: SQV00DR008


Each SQDR replication subscription is registered in SQL Server as a SQL Server Agent job. This allows an administrator to configure a custom alert for an SQDR replication using the SQL Server Agent job notifications. This document explains how to configure job notifications, such as to notify an operator via email, pager email, or net send alerts when an SQDR replication fails, succeeds, or completes.

Note that email or pager alerts require that the SQL Mail Support Service is enabled and configured to be able to send outgoing email. Refer to the SQL Server Books Online for more information on SQL Mail.


  1. Launch the SQL Server Enterprise Manager.
  2. Expand the SQL Server instance that is managing the SQDR Control Database, and expand the Management folder.
  3. Select the SQL Server Agent service, right-click, and select Start if the service is not already running.
  4. Expand the SQL Server Agent and select Jobs.
  5. In the right pane, locate the job associated with the SQDR replication you wish to configure with a notification alert. An SQDR subscription or group appears as a SQL Server Agent job with a prefix of SQDR. Groups appears as SQDR:/group_name and individual subscriptions appear as SQDR:source_name/subscription_name.
  6. Highlight the job, right-click, and select Properties.
  7. On the Notifications tab of the properties, select one or more alerts, specifying the operator to contact and whether the alert should be sent when the job fails, succeeds, or completes. Click Apply or OK to save changes to the job properties.


The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.