SQL defaults to 0 which I think checkpoints every 60 seconds or so.. and to me unless you have a DB that does not scale well to the task and has massive writes and a poorly configured disk system ...

But SQL Server itself provides you with no way to see what's in the transaction log. If something goes wrong with your database, you can restore from a backup -- but there's no way to see in ...

As you restore each log backup, the [!INCLUDE ssde_md] reapplies all the modifications recorded in the log to roll forward all the transactions. When the last log backup is restored, the [!INCLUDE ...

Delayed durability was announced late in the SQL Server 2014 development cycle, but offers something that many SQL Server professionals have wanted for years—the ability to disable transaction logging ...

He kinda answered it Coleman. You'll use the transaction logs to do restores between backups so really it is up to your comfort level.

No problem; right-click, select Undo Transaction, and Log Explorer will generate a SQL Script for you that re-inserts the deleted data. You can run the script directly from Log Explorer or from other ...

But SQL Server itself provides you with no way to see what's in the transaction log. If something goes wrong with your database, you can restore from a backup -- but there's no way to see in ...

Enter Log Explorer. The process is simplicity itself. You choose a server, a database, and a transaction log (either live or backed up). Then you can view every transaction in the log -- what happened ...