Delayed durability offers something that many SQL Server professionals have wanted for years-the ability to disable transaction logging. Why turn off the transaction log? You can accelerate ...

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

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

Using the Transact SQL ALTER DATABASE statement to shrink the transaction log file Open SQL Server Management Studio (SSMS) and click Query Analyzer to open the Query Analyzer window.

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.

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.

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

Take advantage of the open source library Serilog to log your ASP.NET Core application’s data to SQL Server or another database target.