High Virtual Log File (VLF) Count Detected

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.

How to Reduce the Number of Virtual Log Files in SQL Server

The simplest way is to shrink and then grow the log file; although this isn't the best. Read this article from Kimberly Tripp for a more considered approach.

DBCC SHRINKFILE(WhippetWorks_Log, TRUNCATEONLY)
GO
ALTER DATABASE WhippetWorks MODIFY FILE (NAME = WhippetWorks_Log, SIZE = 512MB)
GO

Further Reading

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

​Transaction Log Physical Architecture | Microsoft Docs

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