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,828 reads
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forgive me for the title. Mentally I’m 12. When I started my current day...
Comments posted to this topic are about the item Microsoft Security Changes and SQL...
Comments posted to this topic are about the item Expanding into Print
Comments posted to this topic are about the item Downtime Caused by the Postgres...
In SQL Server 2025, what is returned by this code:
SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled. See possible answers