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?
Backups Log truncation cannot occur during a backup or restore operation. In SQL Server 2005 and later, you can create a transaction log backup while a full or differential backup is occurring, but ...
Transaction logs are a vital yet often overlooked component of database architecture. They are often forgotten because they are not something actively maintained like the schema contained within a ...
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 ...
System Center Data Protection Manager (DPM) provides backup and recovery for SQL Server databases. In addition to backing up SQL Server databases, you can run a system backup or full bare-metal backup ...
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 ...
What do you do when you can't avoid huge transaction logs in SharePoint and your files are too large? Last month, I wrote about how to avoid having ginormous transaction logs within SharePoint ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results