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,815 reads
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
By Steve Jones
I saw some good reviews of the small gemma3 model in a few places...
Comments posted to this topic are about the item Create an HTML Report on...
Comments posted to this topic are about the item SQL Server Advanced Troubleshooting and...
Comments posted to this topic are about the item T-SQL Fundamentals