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

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is ...

I would like to know how transaction log size is managed. I now know after some reading that I can checkpoint the database in order to allow dirty pages to write from ram to disk.I also know now ...

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is). But ...

In SQL Server 2005 and later, you can create a transaction log backup while a full or differential backup is occurring, but the log backup will not truncate the log due to the fact that the entire ...

Delayed durability offers something that many SQL Server professionals have wanted for years-the ability to disable transaction logging. Why turn off the transaction log? You can accelerate ...

The transaction log file contains the SQL Server transactions of the database. It basically records the database transactions and the changes made by the transactions to the database. The logs are ...

We have to perform this backup of the transaction log using either SQL Server Management Studio (SSMS) or T-SQL.

The transaction logs hold temporary data and just deleting or misplacing these files will impact the health of the database. So, to truncate the transaction logs without backup, you need to find a way ...

Backing up SQL Server is a standard practice, but knowing which recovery model to use can be confusing. Use these tips to get started with your backup strategy.