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,820 reads
By Brian Kelley
This was announced last week at Microsoft Ignite and it's been covered by others...
By Rayis Imayev
"Dave: Open the pod bay doors, HAL.HAL: I’m sorry, Dave. I’m afraid I can’t...
By Steve Jones
Redgate acquired a data modeling tool from Vertabelo recently and I wanted to explore...
Comments posted to this topic are about the item The Ending Substring
Comments posted to this topic are about the item Done is Better than Good,...
Comments posted to this topic are about the item Configuring the On-Premises Data Gateway:...
In Azure SQL Database and SQL Server 2025, if I run this, what is returned?
SELECT '[' + SUBSTRING('Steve Jones', 7) + ']' See possible answers