Analyzing your transaction log files directly can provide a wealth of information. Tools like SQL Server Management Studio (SSMS) offer functions to view log contents.

Lumigent calls this application a "transaction analysis and data recovery solution for Microsoft SQL Server." I call it an essential tool for the SQL Server 7.0 or SQL Server 2000 DBA whose users ...

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

From that point forward, transaction logs are periodically sent to the other server where they are automatically restored in the stand-by database. This keeps a hot spare of the server available.

In SQL Server, the transaction log is a critical component that records all transactions and the database modifications made by each transaction. This log plays a vital role in data recovery ...

[!INCLUDE SQL Server] Every [!INCLUDEssNoVersion] database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a ...

Lumigent calls this application a "transaction analysis and data recovery solution for Microsoft SQL Server." I call it an essential tool for the SQL Server 7.0 or SQL Server 2000 DBA whose users ...

So I'm trying to figure out when I should be backing my transaction logs relative to my full/diffs. It seems like right after would be when I'd want to have the checkpoint happen, or does it ...