Understanding and Managing Transaction Logs--Transaction Log Logical Architecture-优快云博客

本文详细介绍了 SQL Server 2005 的事务日志机制，包括日志记录如何通过逻辑顺序号 (LSN) 进行标识及链接，以及在回滚操作中如何利用这些日志记录进行前滚或后滚处理。此外还讨论了不同类型操作的日志记录方式，例如逻辑操作和前后影像记录，并解释了如何通过日志记录来支持事务的完整恢复。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The SQL Server 2005 transaction log operates logically as if the transaction log is a string of log records. Each log record is identified by a log sequence number (LSN). Each new log record is written to the logical end of the log with an LSN that is higher than the LSN of the record before it.

Log records are stored in a serial sequence as they are created. Each log record contains the ID of the transaction that it belongs to. For each transaction, all log records associated with the transaction are individually linked in a chain using backward pointers that speed the rollback of the transaction.

Log records for data modifications record either the logical operation performed or they record the before and after images of the modified data. The before image is a copy of the data before the operation is performed; the after image is a copy of the data after the operation has been performed.

The steps to recover an operation depend on the type of log record:

Logical operation logged
- To roll the logical operation forward, the operation is performed again.
- To roll the logical operation back, the reverse logical operation is performed.
Before and after image logged
- To roll the operation forward, the after image is applied.
- To roll the operation back, the before image is applied.

Many types of operations are recorded in the transaction log. These operations include:

The start and end of each transaction.
Every data modification (insert, update, or delete). This includes changes by system stored procedures or data definition language (DDL) statements to any table, including system tables.
Every extent and page allocation or deallocation.
Creating or dropping a table or index.

Rollback operations are also logged. Each transaction reserves space on the transaction log to make sure that enough log space exists to support a rollback that is caused by either an explicit rollback statement or if an error is encountered. The amount of space reserved depends on the operations performed in the transaction, but generally is equal to the amount of space used to log each operation. This reserved space is freed when the transaction is completed.

The section of the log file from the first log record that must be present for a successful database-wide rollback to the last-written log record is called the active part of the log, or the active log. This is the section of the log required to do a full recovery of the database. No part of the active log can ever be truncated.

From http://technet.microsoft.com/en-us/library/ms180892(SQL.90).aspx