January 7, 2013 at 1:41 pm
In a very busy OLTP environment I have typical transactional replication setup where the publisher, distributor, and the subscriber resides on 3 separate servers. There are several hundred articles being replicated...
In times where the server is "busy" and replication falls behind, does anyone know of a way to determine how MSSQL chooses to process each article? I know it isn't alphabetical or by number of replicated commands, but am puzzled as to how it does this.
Does any one else have experience with this?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
January 7, 2013 at 3:12 pm
I am pretty sure it is based on how the transactions are committed to the log, per the Log Reader Agent traversing the log. Otherwise there could be all sorts of nastiness on the subscriber if transactions were committed in a different order than they were committed on the publisher.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply