Transaction logging

A database or table is said to have or use transaction logging when SQL data manipulation statements in a database generate logical-log records.

The database-logging status indicates whether a database uses transaction logging. The log-buffering mode indicates whether a database uses buffered or unbuffered logging, or ANSI-compliant logging. For more information, see Database-logging status and Manage the database-logging mode.

When you create a database, you specify whether it uses transaction logging and, if it does, what log-buffering mechanism it uses. After the database is created, you can turn off database logging or change to buffered logging, for example. Even if you turn off transaction logging for all databases, the database server always logs some events. For more information, see Activity that is always logged and Database logging in an X/Open DTP environment.

You can use logging or nonlogging tables within a database. The user who creates the table specifies the type of table. Even if you use nonlogging tables, the database server always logs some events. For more information, see Table types for HCL OneDB.