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,834 reads
Every PostgreSQL migration eventually hits the same fork in the road. The database is...
By Steve Jones
I’m off on vacation today. Which is a little weird as I just got...
By Arun Sirpal
Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...
Comments posted to this topic are about the item Have you done a Mid...
Comments posted to this topic are about the item From SQL Server On-Premises to...
Comments posted to this topic are about the item Independence Day 2026
In the original Independence Day movie (1996), what type of computer did Jeff Goldblum use to connect to the alien mainframe? Take a guess, don't look it up or ask AI.
See possible answers