Transactions requiring disk I/O, such as flushing dirty pages from the buffer pool or flushing logs from the log buffer, may wait.
要求磁盘I/O 的事务，例如刷新缓冲池中的脏页或者刷新日志缓冲区中的日志，可能需要等待。
In this strategy, once the last primary log file is filled in the log directory, new transactions will be written to the first log file thereby overwriting existing log data.
在此策略中，一旦日志目录中最后一个主日志文件被写满了，就会将新的事务写到第一个日志文件中，从而覆盖现有的日志数据。
If the system fails, the first thing it does upon restart is to reapply the effects of any committed transactions that are present in the log but whose data blocks have not yet been updated.
如果系统出现故障，重新启动时要做的第一件事就是重新应用所有已提交事务的作用，所有这些已提交的事务都位于日志中，但是它们的数据块尚未更新。
In contrast to circular logging, the archival logging process creates a new log file when the last log file is filled so that future transactions will not overwrite existing log files.
与循环日志记录相比，当最后一个日志文件写满时，归档日志记录过程会创建一个新的日志文件，这样将来的事务就不会覆盖现有的日志文件。
This is common in business events when the database of all events is regarded as a log of the business transactions, so anything that cannot be logged must not happen.
在业务事件中通常认为所有事件的数据库是业务事务的记录，因此任何不能记录的事件就一定没有发生。
So the type of connection being established does not matter because the act of booting the database will recover any incomplete transactions in the transaction log in order to preserve data integrity.
所以正在建立的连接的类型无关紧要，因为数据库的启动将恢复事务日志中所有未完成的事务，以便保持数据完整性。
So if your application calls a file that has unusually long transactions, it may be wise to include frequent commits based upon your log Settings, or to update your database logging parameters.
因此，如果您的应用程序调用具有罕见长事务的文件，根据您的日志设置包含频繁的提交操作，或者更新数据库日志记录参数，也许是好办法。
Between checkpoints, transactions are written to a transaction log and, if the system crashes, transactions are recovered from the transaction log.
在检查点之间的事务被写入到一个事务日志中，并且，如果系统发生崩溃，事务将从事务日志中恢复。
A transaction runs and USES up all five primary log files but is still logging transactions.
事务正在运行，并用完所有五个主日志文件，但仍将记录事务。
This change was introduced to enable peer recovery of transaction log to complete in-doubt transactions when the machine hosting the transaction log crashes.
该变更的引入可以使得寄存事务日志的机器崩溃时，能够利用事务日志的同等恢复来完善不确定的事务。
Transactional RMs achieve durability with acceptable performance by summarizing the results of multiple transactions in a single transaction log.
事务RM通过在一个事务日志中记录多个事务的结果，获得持久性以及可接受的性能。
Crash recovery is the processing of the log files, making sure all committed transactions are written to disk and uncommitted transactions are rolled back.
崩溃恢复是对日志文件进行处理，确保所有已提交的事务被写到磁盘，所有未提交的事务被回滚。
If transactional high availability is not in use, no requirement exists to specify the transactions recovery log directory.
如果没有使用事务的高可用性，无需指定事务恢复日志目录。
A log can be reused in circular logging as long as it only contains information about transactions that have already been committed and externalized to the database disk.
只要日志中包含关于已经提交并外部化到数据库磁盘上的事务的信息，就可以以循环日志的形式重用该日志。
In circular log mode, transactions will write to the log in a circular manner.
在循环日志模式中，事务以循环方式写到日志中。
The additional log disk writes, most of which take place at the federated server, represent the greatest performance impact on single-site transactions of enabling F2PC.
附加的日志磁盘写大多数发生在联邦服务器上，对于启用 F2PC的单站点事务有着最显著的性能影响。
These new transactions will continue to overwrite each old log file in sequence.
这些新事务会继续依次覆盖每个旧日志文件。
If the aim is to speed up individual transactions, then zooming the GC log in on the period of a transaction will give suitable information.
如果目标是加快各个事务的速度，则在某段事务上放大gc日志将会提供合适的信息。
In the event of a system failure, transaction log recovery can apply or undo only those transactions not written to disk at the time of the failure.
在系统失败时，事务日志可以应用或取消失败时没有写入磁盘的那些事务。
Transaction log backup — Backs up all of the transactions performed against the database after the last successful full backup or transaction log backup is completed.
事务日志备份——备份所有执行的事务日志(在上次完全备份之后执行的)。
The files used to log the transactions are called the transaction logs.
用于记录事务的文件叫作事务日志。
This utility USES slicing to delete entries in the audit log table; that is, only the specified number of entries are deleted in a series of single transactions.
此实用程序使用slicing来删除审核日志表格中的条目；也就是说，在一系列单独的事务中只可以删除指定的条目数量。
With transaction logging, Domino posts transactions (or writes) to a series of log files prior to allowing any updates to the database.
通过事务日志，Domino在允许数据库更新之前，将事务发布(或者说写入)到日志文件系列。
This parameter only causes an allocation of log files when the logprimary value is exceeded, which most likely can happen during a series of long uncommitted transactions.
该参数只会当超过logprimary值时才会分配日志文件，这种情况最有可能在一系列长时间未提交的事务期间发生。
Logging scalability - for those who have a penchant for extremely long transactions, DB2 has increased the maximum active log space from 32 GB (version 7.2) to 256 GB.
日志记录可伸缩性—对于那些喜欢使用非常长的事务的人，DB 2已经将最大活动日志空间从32GB (V7.2)增加到256 GB。
Log transactions for auditing and non-repudiation.
用于审计和不可抵赖性的日志事务。
The relaxed durability setting means that a transaction is written to the log when the server is less busy or when the server can write several transactions at the same time.
持久性设为relaxed意味着在服务器不太忙的时候，或者在服务器可以同时写多个事务的时候，才将事务写到日志中。
Select "Circular" for the logging style to continuously re-use the log files and overwrite the old transactions.
选择“Circular”作为日志样式，以持续重用日志文件并重写原来的事务。
At this point, it is guaranteed that there are no transactions that appear as committed in one log, but not committed in another log.
此点保证不存在这样的事务：在一个日志中显示为已提交，在另一个日志中显示为未提交。
We measured loads by the number of database transactions conducted, not by Web pages visited, and we measured local resources by using an ongoing vmstat log.
我们通过所进行的数据库事务的数量来衡量负载，不以所访问的Web页面来衡量，并且我们通过被记录的vmstat日志来衡量本地资源。
应用推荐