The information in this article applies to:
SUMMARYListed below are various reasons why the transaction log fills up and never gets truncated even though the "trunc. log on chkpnt" option is set to true and regular checkpoints are done during processing. MORE INFORMATION
An unbounded update fills up the log; that is, there is no WHERE clause on
the UPDATE statement. Since a transaction (either user declared or
implicit) must be able to be entirely rolled back or committed as a whole,
the log must be large enough to maintain all information for the
transaction. Thus, even when truncating the log, it is possible to fill the
log if it is too small for a single large transaction.
Additional query words: Windows NT
Keywords : kbother SSrvGen SSrvWinNT |
Last Reviewed: March 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |