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

Welcome to this new series -- in this column, I hope to impart some quick, short tips that will help you make quick work of managing and administering your SQL Server databases. First up is an ...

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

With SQL Server 2000, there are myriad choices for backing up your database. Whether your database is small and changes infrequently or very large and changes rapidly, there is a backup strategy to ...

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

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

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

I would like to ask about transaction log backups. I have a transaction log that is around 16gigs I have started to do full database backups every night. To my understanding a full database backup ...