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?

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

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

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

When the creation and configuration of a Recovery Services vault is complete, discovering databases and configuring backup is a two-step process. During the backup configuration, if the SQL VM and its ...

We have the following set up on our SQL servers:<BR><BR>Recovery model is full (for dbs being backed up)<BR>A full backup of the specified database Mon - Fri, no Transaction log backup included in the ...

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