Performance Considerations of FORCE LOGGING Mode

FORCE LOGGING mode results in some performance degradation.

visual studio net training courses malaysia

If the primary reason for specifying FORCE LOGGING is to ensure complete media recovery, and there is no standby database active, then consider the following:

  • How many media failures are likely to happen?
  • How serious is the damage if unlogged direct writes cannot be recovered?
  • Is the performance degradation caused by forced logging tolerable?

Microsoft system center certification training courses malaysia

If the database is running in NOARCHIVELOG mode, then generally there is no benefit to placing the database in FORCE LOGGING mode. Media recovery is not possible in NOARCHIVELOG mode, so if you combine it with FORCE LOGGING, the result may be performance degradation with little benefit.

Microsoft sql server certification training courses malaysia

Starting with Oracle Database 18c, the following two new nologging clauses are introduced, which enable non-logged operations to be carried out and have Active Data Guard standby databases receive all the data, thus preventing performance degradation caused by large redo log generation by the FORCE LOGGING mode:

  • STANDBY NOLOGGING FOR DATA AVAILABILITY
  • STANDBY NOLOGGING FOR LOAD PERFORMANCE

Microsoft sharepoint certification training courses malaysia

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *