History of actions executed by a database management system.
1Truncating your transaction log is therefore not acceptable for most production systems.
2Of course, you must be careful where you back up your transaction log.
3The long-term solution is to move the transaction log to a new disk.
4Each storage engine has its own transaction log for this purpose.
5The after image of the page is recorded in the transaction log buffer.
6You also need to ensure that InnoDB's transaction log files match its tablespace files.
7The after image of the page is now flushed to the physical transaction log.
8The transaction log is the record of all the changes made to a database.
9In its simplest form, a transaction log backup like this:
10If the transaction log does fill up, there are several options to truncate it:
11I wake my computer and call up the transaction log.
12However, because you are truncating your transaction log, changes made on multiple days are unavailable.
13Moving the transaction log to a dedicated disk can reduce-althoughnot eliminate-thetransaction log overhead.
14After this completes, apply each transaction log starting with the oldest and finishing with the newest.
15A given page may be changed several times; replaying the transaction log also changes it several times.
16Recording the change in the transaction log buffer before actually making the change is a safety measure.
Translations for transaction log