As we can see in the video TSQL: Get Number of VLFs, we can obtain the number of VLFs easily but this practice can quickly devolve into busy-work that generates little to no results. Most log issues are not solved through micro-management of logs, even if that feels good or feels productive (it's not). A significant number of log issues come from misapplying architecture to a problem (ie: using OLTP logging for an OLAP database).
Some things we see in the video:
- What are VLFs and where can we find them
- Techniques to save this
- When this could be an issue - if it is
Check out the highest-rated Automating ETL course on Udemy, if you're interested in data.
Another point made in this video worth considering is how we approach teaching our developers about their OLTP/OLAP transactions. Developers have a tendency to create a solution to the problem, but possibly inviting other problems in their solution. I suggest some training for these situations to help them get a feel for the appropriate development technique for their environment.