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

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

So I'm trying to figure out when I should be backing my transaction logs relative to my full/diffs. It seems like right after would be when I'd want to have the checkpoint happen, or does it ...

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

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.

The next version of Microsoft’s relational database management system (RDMS) promises to bring immense performance gains to online transactional processing systems. SQL Server 2014 will come with a ...

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.

Lumigent calls this application a "transaction analysis and data recovery solution for Microsoft SQL Server." I call it an essential tool for the SQL Server 7.0 or SQL Server 2000 DBA whose users make ...