Chapter 37. High-performance transactional replication
The purpose of this chapter is to educate DBAs on how to get maximum performance from their high-performance transactional replication topology across all versions and editions. Most DBAs are concerned with latency—in other words, how old the transactions are when they are applied on the Subscriber.
To set expectations, you should know that the minimum latency of any transactional replication solution will be several seconds (lower limits are between 1 and 2 seconds). Should you need replication solutions which require lower latencies, you should look at products like Golden Gate, which is an IP application that piggybacks off the Log Reader Agent.
Focusing solely on latency will not give you a good indication of replication performance. The nature of your workload can itself contribute to larger latencies. For example, transactions consisting of single insert statements can be replicated with small latencies (that is, several seconds), but large batch operations can have large latencies (that is, many minutes or even hours). Large latencies in themselves are not necessarily indicative of poor replication performance, insufficient network bandwidth, or inadequate hardware to support your workload.
Consequently, in this study we’ll be looking at the following:
