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,825 reads
By John
Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....
By Steve Jones
A customer was asking about what certain items in Redgate Monitor mean. They have...
By Brian Kelley
Pass or fail, act on your certification test results.
I have table: t1 in schema1 with 19 billion records. I have another table...
Comments posted to this topic are about the item Minimally Viable Security
Comments posted to this topic are about the item Encoding NULL
What is returned from this code in SQL Server 2025?
SELECT BASE64_ENCODE(NULL)See possible answers