Aaron also provides a great many links to other resources that discuss the inner workings of the SQL Server transaction log, ways to tune it for maximum performance, and ways to monitor the ...

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

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

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

If left alone, this ginormous transaction log file will continue to grow until it reaches the maximum size set by the SQL Server DBA, or until the physical drive containing the transaction log ...

If the transaction log and database are in the same device you can't do a transaction log dump. In this case you need do a Truncate Log on Checkpoint. You also can't dump the log if the Select ...

Denny's SQL Secrets Exploring SQL Server's Distributed Transactions Here's what you need to know about distributed transaction and when you should use one. By Denny Cherry 02/27/2014 ...

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

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