Counting Unreplicated Commands and Transactions Someone asked me a question via Twitter today that I couldn’t possible answer 40 characters at a time. The question was about how to get the count of unreplicated transactions and commands from teh distribution server without using system views. Well, I do use one system view, but only because replication relies on the same view, sys.servers. The Question @SQLSoldier – Was told you were the guru … lookin for query to get undelivered cmds

SQL Server 2008 SP1 To Old for Replication? We are in the middle of a platform upgrade project at work, and I was setting up replication on a newly flattened and rebuilt server with Windows Server 2008 R2 and SQL Server 2008 SP1. I remoted into the publisher server to set up replication. When I expanded the Local Publications and Local Subscriptions nodes under Replication in Object Explorer, I got an odd error: Operation not supported on version 10.0. (Microsoft.SqlServer.SqlEnum)

If you’ve ever had to deal with errors in Replication Monitor, your first experiences with it probably involved confusion. Sometimes the error messages are too generic and do not help you find a resolution. Replication Monitor also tells you the command that failed. This clears up everything, right? The command reported by Replication Monitor will look something like this: (Transaction sequence number: 0x0001C7A40000AAE700C700000000, Command ID: 1) Helpful!! Right? Well, actually, it is very helpful. What to do with it? There

Measuring Transactional Replication Latency Without Tracer Tokens SQL Server 2005 introduced Tracer Tokens (SQL 2005 | SQL 2008), a new methodology for programmatically measuring replication latency in transactional replication. To measure latency with a tracer token, you simply insert a tracer token at the publisher. The replication process will trace the token as it moves through the steps of the process and report back how long it took for the token to reach the distributor and the subscriber. Sounds great,