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

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

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

SQL Server transaction logs A transaction log is a sequential record of all changes made to the database while the actual data is contained in a separate file.

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

If the transaction log is growing too large then you should increase the frequency of log backups. (The Full database backup does not actually truncate the transaction log at all).

If you have accidently deleted data from database tables in MS SQL Server, you can restore the deleted data (tables) using Log Sequence Number (LSN). But for this, you need the transaction backup file ...

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