AlwaysOn Availability Group - Synchronous-commit with delayed log hardening mode - by Ola Hallengren

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 804223 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 10/1/2013 12:17:11 PM
Access Restriction Public


Consider this scenario: You are running Availability Group in Synchronous-commit mode between two independent datacenters. You cannot have any data loss and the application is very latency critical.

I would like to have an option so that the transaction is committed, when it is in memory on both replicas. The hardening of the log to disk can be delayed.

If one of the servers would crash, so that you are running on only one server, then the hardening of the log should no longer be delayed.

This can be considered safe if the datacenters are fully independent (including power). It is then very unlikely that you lose both replicas at the exact same time.

Sign in to post a comment.
Posted by Microsoft on 10/5/2013 at 1:07 PM

Thanks for your feedback. As we had discussed, delyaed durability does not provide this guarantee and can potentially cause data loss. This is something we have planned for SQL Server 2014. We will consider this in a future release