<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>How a log file structure can affect database recovery time</title><link>http://blogs.msdn.com/psssql/archive/2009/05/21/how-a-log-file-structure-can-affect-database-recovery-time.aspx</link><description>We frequently come across situations where databases take a long time to recover. A common scenario is where the recovery process has to roll forward or back several transactions for a database after a SQL Server restart. However, you might also see one</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How a log file structure can affect database recovery time | Microsoft Share Point</title><link>http://blogs.msdn.com/psssql/archive/2009/05/21/how-a-log-file-structure-can-affect-database-recovery-time.aspx#9634194</link><pubDate>Thu, 21 May 2009 22:22:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9634194</guid><dc:creator>How a log file structure can affect database recovery time | Microsoft Share Point</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoft-sharepoint.simplynetdev.com/how-a-log-file-structure-can-affect-database-recovery-time/"&gt;http://microsoft-sharepoint.simplynetdev.com/how-a-log-file-structure-can-affect-database-recovery-time/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: How a log file structure can affect database recovery time</title><link>http://blogs.msdn.com/psssql/archive/2009/05/21/how-a-log-file-structure-can-affect-database-recovery-time.aspx#9640443</link><pubDate>Mon, 25 May 2009 16:00:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9640443</guid><dc:creator>grahamk</dc:creator><description>&lt;p&gt;I have a demo of how this can affect database mirroring with sample code here &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/grahamk/archive/2008/05/09/1413-error-when-starting-database-mirroring-how-many-virtual-log-files-is-too-many.aspx"&gt;http://blogs.msdn.com/grahamk/archive/2008/05/09/1413-error-when-starting-database-mirroring-how-many-virtual-log-files-is-too-many.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: How a log file structure can affect database recovery time</title><link>http://blogs.msdn.com/psssql/archive/2009/05/21/how-a-log-file-structure-can-affect-database-recovery-time.aspx#9642505</link><pubDate>Wed, 27 May 2009 01:38:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9642505</guid><dc:creator>Kendra Little</dc:creator><description>&lt;p&gt;My understanding is that for large log files, shrinking the file down and then growing it back out in one operation can result in a different problem wherein there are too *few* VLFs for the database. I believe that this can result in problems clearing the log. I have been following Kimberly Tripp's recommendation to re-grow the log file in a given unit: &lt;a rel="nofollow" target="_new" href="http://www.sqlskills.com/BLOGS/KIMBERLY/post/Transaction-Log-VLFs-too-many-or-too-few.aspx"&gt;http://www.sqlskills.com/BLOGS/KIMBERLY/post/Transaction-Log-VLFs-too-many-or-too-few.aspx&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Can you please comment on this?&lt;/p&gt;
</description></item></channel></rss>