Introduction
When SQL Server commits a transaction, it doesn’t just update data in memory. It also writes a record to the transaction log on disk. Only after this log is flushed does SQL Server confirm the commit to the client. This extra step ensures that your data is safe. Even if the server crashes a second later, the transaction can still be recovered because it was saved to disk.
That protection comes with a cost. Writing to disk is slower than working with memory. On systems that handle thousands of small transactions per second — like event logging