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

Help! My SQL Server Log File is too big!!! Your email has been sent Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim ...

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

I'm considering dumping our transaction logs to disk more frequently/truncating our logs more frequently. We don't provide up to the second-last successfull transaction restoration in this particular ...

Pity the poor modern DBA, now that SQL Server gets attacked by some of the same scripts that PCs do. Pity the poor modern DBA who has to keep building Microsoft SQL Servers because some idiot vice ...

Q: We use a lot of distributed transactions and we are now investigating database mirroring to provide high availability to one of our critical databases. During our testing, we discovered that ...

Database protection goes far beyond backups; ensuring the quality and consistency of those backups is equally important. Here are the maintenance tasks that will make sure your databases stay in top ...

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