Replication Alerts

This is a listing of replication alerts that are defined by default in SQL Server. You can add alerts to this list to provide notification of events that will impact your system. By default all of these alerts are disabled. You will want to eable all alerts that point to any error condition. Alerts are extremely important if you are utilizing replication. If something goes wrong, you must respond immediately and provide a fix to the problem. This is due to the effect replication can have on your systems. When replication has a problem, you are affecting multiple servers at the same time. Dealing with one server being offline is difficult enough. Having to deal with many servers offline can present technical and political problems you would rather do without. Alerts will notify you of any problems that have occurred and allow you to respond to them. They also offer the benefit of being able to run a job that will correct the problem. Even if you have jobs configured to automate the process of reestablishing replication, you should always be notified of any errors so they can be investigated and hoepfully prevented from happening again.

Three of the most critical are an Agent failure, expired subscription, and validation error. If an Agent fails, your replication system is offline and not functioning. You must figure out why thisAgent is failing and correct the problem. This is normally due to a login or permission problem. If an expired subscription occurs, you need to find out why it never reached the subscriber. When a subscription expires, it will be purged from the distribution database and the subscriber will never receive it. This means the subscriber no longer holds a complete copy of data from the publisher. A validation problem needs to be fixed on the subscriber side. This means someone has placed an object on the table that is rejecting the publisher’s transactions. This normally occurs when someone places a rule, trigger, or unique index on a table that is being published to without being aware of the publication. This can cause data to fail the validation checks that are now in place, but did not exist when replication was started.

Replication Primer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40