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,831 reads
Both SQL Server and PostgreSQL are moving fast into AI territory — and if...
By Steve Jones
We keep adding new AI capabilities to Redgate Monitor, where it makes sense. Check...
By ReviewMyDB
A behind-the-scenes look at Day of Data Jacksonville 2026, the transition from SQL Saturday,...
Hallo all! My problem is this: I have quite a bunch of TSQL scripts...
Comments posted to this topic are about the item Would You Retire Rather Than...
Comments posted to this topic are about the item Vector Search in SQL Server...
Does this run successfully on a SQL Server 2022, US English default installation?
DECLARE @YenAmount MONEY; SET @YenAmount = ¥1500; SELECT @YenAmount AS RawValue;See possible answers