Transaction Logs are a vital part of the Oracle and any other RDBMS technology integrity and recovery mechanism. Without it, an instance will not recover when it crashes and will not start in a consistent state. Excessive transaction log generation is the result of excessive work on the database, but not be a foul, sometimes it can be due to your bad code. This presentation covers the subject of reducing transaction generation using LOGGING and NOLOGGING options, the differences between them, how it happens, how to reduce it, and when to use it. Also, you will find examples and tips regarding each one of them. Logging is crucial to ensure the performance and recoverability of any Cloud RDBMS or in the premises environment.
Want to sponsor? Contact us to find out more.