Transaction log for standalone DB vs AlwaysON availability Group

by Linu1988   Last Updated August 02, 2018 22:06 PM

I have this question on the generation of transaction logs. For a high transaction active DB what is the ratio of log generation if it is a standalone DB and when it is part of SQL Alwayson availability group(synchronous commit).

I am pretty sure it will be high, but how much higher. Rather than doing a test on my own any answer or reference will be helpful.

Note: The perfmon counter do show the numbers for transactions/logs flushed which seems to be really in case of AG. I want to understand if there is a way to limit it as well.



Answers 1


For a high transaction active DB what is the ratio of log generation if it is a standalone DB and when it is part of SQL Alwayson availability group(synchronous commit).

Assuming Full Recovery mode, which AGs require, 1:1. AGs don't require any additional logging beyond what a Full Recovery database already does.

In Simple recovery mode you might have some minimally logged operations, but for a "high transaction active" database, it's unlikely. See eg

SQL Server 2016, Minimal logging and Impact of the Batchsize in bulk load operations

David Browne - Microsoft
David Browne - Microsoft
August 02, 2018 21:57 PM

Related Questions



Transaction Log Truncation with Copy Only

Updated March 28, 2018 17:06 PM


Moving from FCI to DAG

Updated October 19, 2017 14:06 PM