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

SQL Server 2014 hastens transaction ... it selectively moves only the most consulted database tables to memory. In ... even during a system outage—by writing transactions separately to a log file.

SQL Server then assumes that the log flush will eventually happen and, unless you change the default, will push log records to the transaction log as the default 60KB log buffer chunk fills up. (You ...

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.

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

If the transaction log and database are in the same device you can't do a transaction log dump. In this case you need do a Truncate Log on Checkpoint.

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.

The next version of Microsoft’s relational database management system (RDMS) promises to bring immense performance gains to online transactional processing systems. SQL Server 2014 will come ...

Log Explorer unlocks your SQL Server Transaction Logs. A must-have tool for the professional DBA. By Mike Gunderloy; 01/09/2002; Lumigent calls this application a "transaction analysis and data ...