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,882 reads
By Brian Kelley
The concern that a particular technology is going to destroy the world seems to...
The STIG is detailed, which is a good thing, but I found myself wanting...
By Steve Jones
After my session at VSLive last week, I had a few questions from the...
Comments posted to this topic are about the item RegEx Functions III
Comments posted to this topic are about the item Optimized Locking in SQL Server...
Comments posted to this topic are about the item Finely Tuned Models
If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.
See possible answers