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

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

It is these transaction log backups that keep your transaction log file from growing too large. An easy way to make consistent transaction log backups is to include them as part of your database ...

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

But SQL Server itself provides you with no way to see what's in the transaction log. If something goes wrong with your database, you can restore from a backup -- but there's no way to see in ...

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

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

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