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

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

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

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

SQL Server instances, even if equipped with provisions like automatic backup and recovery, are not sufficiently protected against sudden, disastrous situations like multi-site database failure, ...

There isn’t a week that goes by that I don’t hear or read about an organization seeing ginormous transaction log (.ldf) files, while the associated data (.mdf) file is at the size it should be when ...

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 Backup Pro 6 features improved “network resilience to recover interrupted backup operations, self-healing log shipping and a new advanced compression algorithm,” Red Gate claims. “Marketing calls ...

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