From Wikipedia, the free encyclopedia No-force
No-force
A no-force policy is used in transaction control in data- tion log, with the actual changes to the database objects
base theory. The term no-force refers to the disk pages being changes which can be written at a later time.
related to the actual database object being modified. For frequently changed objects, a no-force policy al-
With a no-force policy, when a transaction commits, lows updates to be merged and so reduce the number of
the changes made to the actual objects are not required write operations to the actual database object. A no-force
to be written to disk in-place (forced). policy also reduces the seek time required for a com-
A record of the changes must still be preserved at mit by having mostly sequential write operations to the
commit time to ensure that the transaction is durable. transaction log, rather than requiring the disk to seek to
This record is typically written to a sequential transac- many distinct database objects during a commit.
Retrieved from "http://en.wikipedia.org/w/index.php?title=No-force&oldid=254061429"
Categories:
• Database management systems
• Database stubs
This page was last modified on 25 November 2008 at 18:52. Text is available under the Creative Commons Attribution-
ShareAlike License; additional terms may apply. See Terms of use for details. Wikipedia® is a registered trademark of
the Wikimedia Foundation, Inc., a non-profit organization.Contact us
Privacy policy About Wikipedia Disclaimers Mobile view
1