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

Aaron also provides a great many links to other resources that discuss the inner workings of the SQL Server transaction log, ways to tune it for maximum performance, and ways to monitor the ...

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

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. You also can't dump the log if the Select ...

If left alone, this ginormous transaction log file will continue to grow until it reaches the maximum size set by the SQL Server DBA, or until the physical drive containing the transaction log ...

SQL Server 2012 then borrowed this columnar processing technique for its own use. As an example of how the new SQL Server could speed performance, Kelly explained how a retail chain could benefit ...

We normally think of distributed transactions just within the scope of a SQL Server transaction. However, you can also put things like file system access by a .NET application within a distributed ...

SQL Server 2012 then borrowed this columnar processing technique for its own use. As an example of how the new SQL Server could speed performance, Kelly explained how a retail chain could benefit ...

No problem; right-click, select Undo Transaction, and Log Explorer will generate a SQL Script for you that re-inserts the deleted data. You can run the script directly from Log Explorer or from other ...