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 ...
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?
Some results have been hidden because they may be inaccessible to you
Show inaccessible results