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,634 reads
By Rob Sewell
In the WordPress community, badges aren’t just for scouts.
By James Serra
The new data governance features in Microsoft Purview are now being made generally available...
Sometimes your Microsoft Entra ID account (formerly known as Azure Active Directory) is added...
Comments posted to this topic are about the item New article
Comments posted to this topic are about the item Monitoring Azure Blob Storage
Azure Data Lake Storage Gen 2 is built on ...?
See possible answers