I’ve personally seem some cases where running more than one instance of Replication Monitor while a publication snapshot was being taken also caused blocking. Replication Monitor may run queries to count the number of undistributed commands that may take a while to run and be performance intensive (particularly when things get backed up in the distributor).Replication Monitor is a tool to help you answer the question “how are things doing right now?” It doesn’t baseline or give the kind of historical info that your manager wants to see.The first five links in “Monitoring Replication” in Books Online point to it, after all. When replication is behind, it’s natural to turn to Replication Monitor. Don’t Rely Too Much on Replication Monitor (REPLMON.exe) The fact that it’s potentially unknown means I don’t want to rely heavily on it for monitoring.
I won’t hear back until it reaches its destination or definitively fails. Let’s say my replication is incredibly overwhelmed and I send out a tracer token. There’s a big problem: tracer tokens are too patient. Books Online explains that you can automate them using sys.sp_posttracertoken and report on them using sp_helptracertokenhistory. “Tracer Tokens” were introduced in SQL Server 2005. If you’re just getting started and need an introduction to transactional replication, head over here. Here’s what I learned from that experience about monitoring replication. I was a SQL Server DBA, and if something went wrong in Transactional Replication I needed to find out about it right away and help keep things healthy, day or night. It was the best of times, it was the worst of times.
0 kommentar(er)
