Long write transactions: <number of> log pages per transaction <number of> write transactions, <number of> log pages

The write transactions from the application are very long causing a large number of physical writes to the log. This is not a problem for background applications. However, long write transactions can cause bottlenecks if other sessions are attempting to access SQL objects (lines and tables) locked by the long write transaction. In some cases, very long transactions may cause a delay when a backup requests a checkpoint, because at the time of the checkpoint the system must wait for a COMMIT from every open write transaction. No new write transactions are permitted until the checkpoint is finished, which almost always forces a temporary stop in database operation (all tasks with status Vwait).

This bottleneck cannot be influenced using the database. You can avoid the wait times due to checkpoint requests by running data backups without checkpoints.