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,772 reads
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...
By Steve Jones
I saw a post internally that asked this question: Anyone have a handy powershell...
Comments posted to this topic are about the item GIT Configuration and Automated Release...
Hi, I'm working on cleanup activity of deleting databases that aren't in use or...
Good morning campers! I'm hoping to pick your collective hive brain wrt Veeam /...
How do I disable all the indexes on the dbo.Logger table?
See possible answers