备份之后的所有事务日志文件。
高度可用的事务日志恢复。
将事务日志和文件库移动到快速磁盘上。
最好将事务日志保留在其所需的大小。
It's better to leave the transaction log at its needed size.
输入事务日志的路径名称位置（第 1步中分配）。
Enter the path name location of the transaction log (allocated in Step 1).
使用本页面查看该服务器的详细事务日志。
Use this page to view a detailed log of transactions for this server.
收缩应该是数据或事务日志的极少数运算。
Shrink should be a rare operation on data or transaction logs.
不过，有时事务日志备份要比完全备份还大。
However, sometimes a transaction log backup is larger than a full backup.
为了获得高可用性和进行故障恢复，我们推荐使用事务日志。
We recommend transaction logging for high availability and failure recovery.
重建可以使用最小日志记录来减少事务日志增长。
REBUILD can use minimal-logging to reduce transaction log growth.
如果事务日志归档模式被启用，那么这个属性将被设为true。
If the transaction log archive mode is enabled, this property will be set to true.
研究结果表明，利用事务日志可以实现无数据丢失的完全恢复。
The result shows that the complete recovery can be implemented by transaction log.
了解如何使用事务日志、多种mail . box和多种磁盘驱动控制器来提高性能。
Learn how to increase performance using transaction logging, multiple mail.boxes, and multiple disk drive controllers.
它把记录写入恢复日志，增加事务状态信息。
It writes records to a recovery log, plus transaction state information.
日志包含可以恢复的最后一次备份之后的所有事务。
The logs contain all transactions since the last backup you were able to restore.
这些新事务会继续依次覆盖每个旧日志文件。
These new transactions will continue to overwrite each old log file in sequence.
对于长期运行的事务，常常需要创建容量更大的主日志。
For long-running transactions, often there is a need to create primary logs with bigger capacity.
它会前滚到日志的末尾，达到最近的事务模式。
It will roll forward to the end of logs, to the very last transaction mode.
在循环日志模式中，事务以循环方式写到日志中。
In circular log mode, transactions will write to the log in a circular manner.
事务审计信息日志(TAIL)。
事务性日志记录的类型不止一种吗？
不涉及事务原子性的日志操作。
图5：事务支持的日志服务架构。
代理日志将每个代理事务存储在日志中的一行上。
The agent log stores each agent transaction on a single line in the log.
你可能需要复习6.033的第8章，特别在我们讨论事务和日志期间。
You may wish to review 6.033 Chapter 8, especially during our discussion of transactions and logging.
你可能需要复习6.033的第8章，特别在我们讨论事务和日志期间。
You may wish to review 6.033 Chapter 8, especially during our discussion of transactions and logging.
应用推荐