<?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>When should you rebuild the transaction log?</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx</link><description>10 points if you answered "don't be daft, never! " and minus several million is you answered anything else. Yes, if you have no backups and your hardware has corrupted your transaction log then you have no choice but to rebuild it, but this should never</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How banks can steal your money</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#632636</link><pubDate>Thu, 15 Jun 2006 22:08:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:632636</guid><dc:creator>SimonS SQL Server Stuff</dc:creator><description>If you ever visit the forums you will learn many ways to manage your SQL Server. Some of these are good...</description></item><item><title>Ta da! Emergency mode repair</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#636106</link><pubDate>Sun, 18 Jun 2006 18:15:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:636106</guid><dc:creator>SQL Server Storage Engine</dc:creator><description>Emergency mode repair? In a couple of previous posts I explained how the two worst things you could do...</description></item><item><title>re: When should you rebuild the transaction log?</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#1383878</link><pubDate>Sat, 30 Dec 2006 11:44:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1383878</guid><dc:creator>phront</dc:creator><description>&lt;p&gt;what to do when mdf &amp;amp; log are bad &amp;nbsp;and if dbcc REPAIR_ALLOW_DATA_LOSS cause assertion at logmgr.cpp with expression (minLSN.m_fSeqNo &amp;lt; lfcb-&amp;gt;lfcb_fSeqNo)? &lt;/p&gt;
</description></item><item><title>How banks can steal your money</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#4341809</link><pubDate>Sun, 12 Aug 2007 02:51:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4341809</guid><dc:creator>SimonS SQL Server Stuff</dc:creator><description>&lt;p&gt;If you ever visit the forums you will learn many ways to manage your SQL Server. Some of these are good&lt;/p&gt;
</description></item><item><title>re: When should you rebuild the transaction log?</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#6548419</link><pubDate>Tue, 27 Nov 2007 14:09:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:6548419</guid><dc:creator>vibemill</dc:creator><description>&lt;p&gt;Hey Paul, you say &amp;quot;don't be daft, never!&amp;quot; &lt;/p&gt;
&lt;p&gt;I have a sql 2005 express database that is 1.4 gb ,,, the transaction file grew to 84 gb ... sql is pathetic!!!&lt;/p&gt;
&lt;p&gt;Oii, enough already!!! there is no way that the transaction file should with default swettings grow to that ridiculous size. the database is backed up every day. It is not mission critical to the extent of a live transaction bank account database or airline reservation database. Even if it was, the size of the transaction file should NOT grow to 60 times the size of it's database. You have nothing to be proud of or smart about ... FIX IT!!!&lt;/p&gt;
&lt;p&gt;shalom, Robert&lt;/p&gt;
</description></item><item><title>re: When should you rebuild the transaction log?</title><link>http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/15/632398.aspx#8992814</link><pubDate>Thu, 09 Oct 2008 16:05:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8992814</guid><dc:creator>cisjokey</dc:creator><description>&lt;p&gt;Hello Dear&lt;/p&gt;
&lt;p&gt;First, thanks for this article!&lt;/p&gt;
&lt;p&gt;To bad to see poeple with no background knowledge, &amp;nbsp;trying to blame you. &lt;/p&gt;
&lt;p&gt;&amp;quot;Don't be daft, never!&amp;quot; is just a great and clean statement.&lt;/p&gt;
</description></item></channel></rss>