A hotfix for slow performance when recovering a database due to excessive VLFs

Happened to catch a hotfix - 2489376 Cumulative Update package 6 for SQL Server 2008 R2:

FIX: Slow performance when you recover a database if there are many VLFs inside the transaction log in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2

If you get message such as the following, you may have a problem:

Analysis of database 'mydatabase' (7) is 0% complete (approximately 1234 seconds remain). This is an informational message only. No user action is required.

The fix is intended for those who haven’t managed their transaction logs well. Of course, the best way to handle is to keep the VLF count at 1000 or below; grow your tlog out from the beginning and you won’t have a problem. Anyway, if you see this message in your logs, go get more info here and get the workaround.

Lee

-----------------

http://support.microsoft.com/kb/2455009