Minimal Undo Logging to Support the Rollback of Data Changes to DGTTs
In DB2 UDB v7, the NOT LOGGED clause was mandatory when creating a DGTT (notice that we used this option in the preceding example). In DB2 UDB v8, this clause is optional and DGTTs are logged by default to support the rollback of a unit of work or a rollback to an application save point. (For the rest of this section, we refer to rollback as either the rollback of a unit of work or the rollback to an application save point.)
The NOT LOGGED option reduces the amount of overhead that a database manager needs to perform to manage a DGTT, but it has its drawbacks. For example, applications leveraging data in temporary tables might require atomicity or the ability to leverage save ...
Get DB2® Version 8: The Official Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
