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

You really didn't read the post did you?<BR><BR>It's not that I'm not doing backups, I'm just not sure how often teh transaction logs should be backed up, and relative to when the full/diff is run ...

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

Every SQL Server database has at least two files; a data file and a transaction log file. The data file stores user and system data while the transaction log file stores all transactions and ...

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

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

So to avoid ginormous transaction logs; don’t use Simple Recovery Model, simply periodically back up the transaction logs so they don’t get too large, and the best time to do this is ...

Using the Transact SQL ALTER DATABASE statement to shrink the transaction log file Open SQL Server Management Studio (SSMS) and click Query Analyzer to open the Query Analyzer window.

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