Transaction logs are a vital yet often overlooked component of database architecture. They are often forgotten because they are not something actively maintained like the schema contained within 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 ...

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

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

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

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

I call it an essential tool for the SQL Server 7.0 or SQL Server 2000 DBA whose users make mistakes. As far as I know, that would be *every* DBA out there. SQL Server, of course, keeps track of ...