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

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

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

I would like to know how transaction log size is managed. I now know after some reading that I can checkpoint the database in order to allow dirty pages to write from ram to disk.I also know now ...

I mentioned NetIQ's new SQL Management Suite of integrated SQL Server management products last issue. This time around, I got the chance to give it a spin. Here are some impressions of the new ...

Take advantage of the open source library Serilog to log your ASP.NET Core application’s data to SQL Server or another database target. Logging is an essential feature for any application, as 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 ...

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

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