It was written for Oracle 7. There is one more reason in my opinion:
A write-ahead log ensures that no data modifications are written to disk before the associated log record.
SQL Server maintains a buffer cache into which it reads data pages when data must be retrieved. Data modifications are not made directly to disk, but are instead made to the copy of the page in the buffer cache.
The modification is not written to disk until either the database is checkpointed, or the modifications must be written to disk so the buffer can be used to hold a new page.
Writing a modified data page from the buffer cache to disk is called flushing the page. A page modified in the cache but not yet written to disk is called a dirty page. At the time a modification is made to a page in the buffer, a log record is built in the log cache recording the modification.
This log record must be written to disk before the associated dirty page is flushed from the buffer cache to disk.
If the dirty page were flushed before the log record, it would create a modification on disk that could not be rolled back if the server failed before the log record were written to disk.
SQL Server has logic that prevents a dirty page from being flushed before the associated log record. Because log records are always written ahead of the associated data pages, the log is called a write-ahead log.
What happens if a power outage occurs? All log cache transaction information will be lost.Optimizing InnoDB Redo Logging. which can be configured dynamically in MySQL Configure the innodb_log_write_ahead_size configuration option .
Books Online: Write-Ahead Transaction Log - Microsoft® SQL Server™ , like many relational databases, uses a write-ahead log.
A write-ahead log ensures that no data modifications are written. Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about transaction processing. A detailed description can be found in most (if not all) books about transaction processing.
MySQL. More than 1 year has passed since last update. InnoDB. 「WAL」（Write Ahead Log（ログ先行書き込み））で更新される。. The concept of Write Ahead Logging is very common to database systems.
This process ensures that no modifications to a database page will be flushed to disk until the associated transaction log records with that modification are written to disk first.
The Write Ahead Log (WAL) is one of the most important components of a database. All the changes to data files are logged in the WAL (called the redo log in InnoDB). This allows to postpone the moment when the modified pages are flushed to disk, still protecting from data losses.