After experiencing weekly CDC failures caused by transaction log issues and logs suddenly chewing up disk space, I found myself repeatedly investigating the same questions: Why is the log so large?

The tail log backup in SQL Server is the last safety net you get when something breaks and you cannot afford to lose even a single committed transaction. It captures the final portion of the ...

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

SQL Server Backup Strategy Many companies say, “We take daily full backup.” But is that really a backup strategy? 🤔 As a SQL DBA, backups are not a task — they are business survival. Here’s a ...

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

Our normal practices for backing up SQL servers is to use the regular SQL backup tools to perform full, differential and transaction log backups and this has always worked fine. Recently we performed ...

In an earlier blog entry, I talked about “Deprecated” code and I highlighted the fact that the BACKUP LOG WITH NO_LOG and BACKUP LOG WITH TRUNCATE_ONLY statements are no longer allowed in SQL Server ...