!! Based on the custom condition : High VLF Count !!
!! Changes : Uses T-SQL, will return for databases that are not part of availability groups and AG Primary replicas only, will not return data for secondary AG database replicas. !!
SQL Server database transaction logs contain multiple virtual log files, or VLFs. The number of VLFs is dictated by the initial size and auto-growth size for the transaction log. Too many VLFs can lead to increased backup/recovery times and possible performance problems.
See the Performance Advisor Disk Space tab for VLF counts for all log files, as well as configured auto-growth size and how many VLFs will result from each auto-growth.
If VLFs are too high, the count can be reset by shrinking and resizing the log. See the "8 Steps" article below for more details and scripts.
See Also:
http://www.sqlskills.com/blogs/kimberly/transaction-log-vlfs-too-many-or-too-few/
http://www.sqlskills.com/blogs/kimberly/8-steps-to-better-transaction-log-throughput/