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?

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

database_transaction_log_bytes_used / 1024 as [Log KB Used], database_transaction_log_bytes_reserved / 1024 as [Log KB Reserved], database_transaction_log_bytes_used ...