TestKing.com has two SQL Server 2005 computers named SQL1 and SQL2. Both servers take part in replication. SQL1 is both the Publisher and its own Distributor of a publication named Pub1. Pub1 is the only publication on SQL1, and SQL2 is the only Subscriber. Your supervisor requests a status report about the replication latencies. Using Replication Monitor on SQL1, you need to find out the current latencies between the Publisher and Distributor as well as between the Distributor and Subscriber.
What should you do?
A.
Select the Subscription Watch List tab for SQL1. View the Latency column for the SQL2 subscription.
B.
Select the All Subscriptions tab for the Pub1 publication. View the Latency column for the SQL2 subscription.
C.
Select the Tracer Tokens tab for the Pub1 publication. Select the Insert Tracer option and wait for the requested latency values for the SQL2 subscription to appear.
D.
Select the Subscription Watch List tab for SQL1. Double-click the SQL2 subscription.
View the duration details on the Publisher to Distributor History tab as well as on the Distributor to Subscriber History tab.
Explanation:
Tracer tokens are a new feature of the transactional replication engine in SQL Server 2005. They are a specialized transactions that is used to gain timing information. Since tracer tokens are picked up by the replication engine and transit with every other transaction, they can be used to determine the amount of time it takes a transaction to move from the publisher to distributor and then from the distributor to each subscriber. With this piece of information, you can now answer the two most predominant questions for replication: How far behind am I and how long will it take to catch up?