High VLF Count

The SQL Server transaction log is made up of multiple Virtual Log Files (VLF), each addressing a portion of the allocated log space. If the log file grows, the number of VLFs will grow too. However, having too many VLFs can negatively impact all performance that uses the transaction log, even including backing up the transaction log itself.

Suggested Action

Reconfigure the transaction log files using the procedures explained in the Resolution section of this article.

Any suggestion from Aireforge should be thoroughly tested before being implemented into production.

Further Reading

​Transaction Log Physical Architecture | Microsoft Docs

Database operations take a long time to complete, or they trigger errors when the transaction log has numerous virtual log files | Microsoft Support

Important change to VLF creation algorithm in SQL Server 2014 | SQLSkills