• Festeron (3/29/2010)


    Tom.Thomson (3/20/2010)


    vk-kirov (3/20/2010)


    Tom.Thomson (3/19/2010)


    But a single select statement may write more pages than can be held in RAM and this means that dirty pages get to disc

    "Insert statement", I believe?

    Yes, of course. Silly me! :blush:

    Can I ask you about the other end of the backup?

    At what point does the backup decide it's time to stop backing up, even though there may be transactions still in flight? Does there come a time when backup decides to stop chasing its tail?

    Or does it not back up anything in the log past the point at which the backup began?

    As far as I know, it stops as soon as it reaches the end of the log file. That means that, in theory, you could envisage a scenario where the log file grows faster than the backup can read it, and the backup won't terminate. Though I am pretty sure that in practice, you'll never be able to make that happen.


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/