Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
1.3.6 Transaction Log

1.3.6 Transaction Log


The transaction log is used to keep track of each file node list (section 2.4) and how much of the list ought to be read. Each file node list can continue for any length, but the transaction log defines the active length. Content past the end represents incomplete transactions. A complete transaction begins with data appended to the file node lists, followed by new entries in the transaction log to reflect the updated state of the file node lists. The final operation for the transaction is to update the transaction count in the header to activate the new transaction entries.

© 2015 Microsoft