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 Steve Jones
At Redgate, we’re experimenting with how AI can help developers and DBAs become better...
I was messing around performing investigative work on a pod running SQL Server 2025...
By Steve Jones
Redgate recently released SQL Compare v16, which included a new feature to work with...
Comments posted to this topic are about the item What is Page Density
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Looking to confirm my understanding of these three products and how they can be...
In SQL Server, there is a concept of page density. This is determined by how much data is stored on each page. What is a page density of 90%?
See possible answers