How do you monitor latency replication?
You can calculate replication latency from Distributor to all Subscribers by querying the tracking tables in the distribution database. The simplest way to check latency is simply to let the replication monitor procedures do the work for you and then pull the data from the replication monitor tables.
What is tracer token in SQL replication?
Tracer tokens were introduced with Sql Server 2005 transactional replication as a way to monitor the latency of delivering transactions from the publisher to the distributor and from the distributor to the subscriber(s) (and as a side-effect, you can also get the time from the publisher to the subscriber(s)).
How to insert tracer tokens in replication monitor?
For information about starting Replication Monitor, see Start the Replication Monitor. Expand a Publisher group in the left pane, expand a Publisher, and then click a publication. Click the Tracer Tokens tab. Click Insert Tracer.
Can a tracer token be entered after failover?
After failover, a tracer token cannot be entered by using the Replication Monitor, however a tracer token entered on the new publisher by using Transact-SQL, is visible in Replication Monitor. For information about starting Replication Monitor, see Start the Replication Monitor.
How to troubleshoot transactional replication latency issues?
Fore more details about tracer tokens refer to this, BOL: http://technet.microsoft.com/en-us/library/ms151846 (v=sql.105).aspx The following is output from sp_replcounters for a good performing environment.
Do you need a tracer token to use quiesce?
For more information, see Quiesce a Replication Topology (Replication Transact-SQL Programming). To use tracer tokens, you must use certain versions of Microsoft SQL Server: The Distributor must be Microsoft SQL Server 2005 (9.x) or later. The Publisher must be SQL Server 2005 (9.x) or later or be an Oracle Publisher.