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

Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim Chapman discusses the perils of not handling SQL Server log growth ...

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

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

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

The system maintains transactional integrity—the guarantee that each completed transaction is saved even during a system outage—by writing transactions separately to a log file.

The system maintains transactional integrity — the guarantee that each completed transaction is saved even during a system outage — by writing transactions separately to a log file.

SQLNitro was recently clocked with a roundtrip speed of 206 milliseconds between traders in Korea and an SQL Server in Exeter, NH. The transaction was 31% faster than any previous test done by the ...