monitoring

This is a direct follow up to my previous post on Tracer Tokens and Replication Latency.


This post will include some simple code to check for excessive latency in your replication and, if appropriate, send out an email informing you of the problem.

After my last post surrounding Tracer Tokens I was told by a friend that it was a little harsh to simply end saying that you can just join to a few system tables and make something meaningful. Therefore I’ve given in and this post will show you how you can use tracer token and system data to your advantage.

If you’re using Transactional Replication then these can be invaluable to you. These are incredibly lightweight, easy to use, and they will help you with all manner of reporting and troubleshooting within your replicated environment.