SQL Server 2012 new high VLFs warning: Important update

Hello all, If you follow this blog, this is another post on VLFs, a topic I’ve covered several times before. If you want to read more about it just click here. Also, all scripts in the VLF posts have been updated to support SQL server 2012. So, back in October I posted about the new…


SQL Swiss Army Knife #10 – VLFs again. What’s your current status?

EDIT (11-01-2011): A parenthesis was missing making the log_size_MB value skewed. Thanks Luis! EDIT (26-03-2012): Updated script for SQL 2012 support. EDIT (19-11-2012): Added information from Fixing VLFs post, namely potential log size after fix, actual number of VLFs, amount of used VLFs, potential number of VLFs after fix, how many growth iterations to achieve…


SQL Swiss Army Knife #9 – Fixing VLFs

Download script here: Fix_VLFs.sql Hello all, Here is another post on SQL scripts that may help DBAs, following the series “SQL Swiss Army Knife”, this time revisiting the topic of VLFs. I blogged on this subject several times before and if you want to read more about it just click here. Anyhow, a few months…


Can log files growth affect DML? Post-CU Update

Hello all, A while back I blogged on how log files can affect DML performance, depending on their structure and growth ratio. It recently came to my attention (thanks Paul Randal) that a fix was published late last February, in KB2455009, aimed at scenarios where one might experience slow performance when recovering a database, if…


Can log files growth affect DML?

Hello all, A while back I blogged here about how a good strategy of log file growth could potentially impact ongoing operations with your SQL Server. It’s known that VLFs (number and size) impact on the performance of such actions as scanning all VLFs for transactions that are marked for replication or log backup operations….


SQL Server and Log File usage

Hello all, I decided to talk about an issue I’ve recently dug a little deeper, and so i will talk about how and why Log files (and their growth strategy) affect recovery times, mirroring, replication, large data changes (batches), leads to disk fragmentation, and ultimately adds stress factors to SQL Server I/O. First of all,…