Generally, you will have no need to worry about the number of virtual log files in your transaction log. However, if you use the default settings for 'auto-grow', you can end up with such 'fragmentation' in your transaction log as to affect performance noticably. How can this be avoided? How can you tell it's a problem? What do you do about it? Greg explains.
2012-11-23 (first published: 2012-05-01)
7,126 reads
2010-08-16 (first published: 2010-03-05)
3,838 reads
By James Serra
Originally published April 2022; substantially updated July 2026. This post is a complete replacement...
The idea behind Azure SQL Developer is for anyone to build, iterate, and test...
By Steve Jones
I’m sure many of you are using AI regularly, perhaps chatting, perhaps using some...
Hello everyone , I am planning to migrate a database from SQL Server 2014...
Comments posted to this topic are about the item SQL Agent Job Automated Change...
Comments posted to this topic are about the item Another Model, More Data Loss
Where do I check for the existence of a Database Master Key (DMK) in SQL Server 2025?
See possible answers