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 ...

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 ...

In SQL Server 2005 and later, you can create a transaction log backup while a full or differential backup is occurring, but the log backup will not truncate the log due to the fact that the entire ...

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.

The transaction log file contains the SQL Server transactions of the database. It basically records the database transactions and the changes made by the transactions to the database. The logs are ...

SQL Server 2012 then borrowed this columnar processing technique for its own use. As an example of how the new SQL Server could speed performance, Kelly explained how a retail chain could benefit ...

SQL Server 2012 then borrowed this columnar processing technique for its own use. As an example of how the new SQL Server could speed performance, Kelly explained how a retail chain could benefit ...

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 ...

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 ...

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is). But ...