pdanes (4/23/2013)
I assume then, that the reading of log records is a one-time event? That is, after doing the primary read, it catches up with the log records once, and doesn't continually go back and check for more transactions that may have accumulated while it was catching up the previous transactions?
It doesn't need to. The data backup plus the additional log records are sufficient to ensure you have a transactionally consistent database, which is the important thing as far as SQL server (and the user, for that matter!) is concerned.