Delayed Durability means that it is possible that there will be transactions that have been reported as committed, and yet aren't written or hardened to the database transaction log. You know this and should be prepared to accept the potential data loss should the system crash or failover. But what if you need to take the system down for some reason? You wouldn't want to lose data as a result of planned outage. So, if your database is using Delayed Durability, you need some way of manually flushing the log to the disk. With SQL Server 2014, there are two ways to do this:

You can also execute a fully durable transaction that makes changes to the same database. This will also force a flush of...