<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.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>Bulk logged recovery model and log backups</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2007/08/19/bulk-logged-recovery-model-and-log-backups.aspx</link><description>This post is inspired from a discussion about bulk logged recovery model and log backup. Some basics: In bulk logged recovery model, some operations can be minimally logged, like: SELECT INTO Index create, rebuild and drop Bulk loading of data The interesting</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Bulk logged recovery model and log backups</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2007/08/19/bulk-logged-recovery-model-and-log-backups.aspx#15189</link><pubDate>Fri, 10 Jul 2009 19:29:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:15189</guid><dc:creator>BlackHawk</dc:creator><description>&lt;p&gt;Tibor,&lt;/p&gt;
&lt;p&gt;Is there any reason to use anything besides Bulk Logged if performing Log Shipping? &lt;/p&gt;
&lt;p&gt;I would assume transaction log backups were being performed at a reasonable rate.&lt;/p&gt;
</description></item><item><title>re: Bulk logged recovery model and log backups</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2007/08/19/bulk-logged-recovery-model-and-log-backups.aspx#15198</link><pubDate>Sat, 11 Jul 2009 08:49:45 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:15198</guid><dc:creator>TiborKaraszi</dc:creator><description>&lt;p&gt;&amp;lt;&amp;lt;Is there any reason to use anything besides Bulk Logged if performing Log Shipping? &amp;gt;&amp;gt;&lt;/p&gt;
&lt;p&gt;I prefer to only use bulk_logged when neccesary. IF you have the db in bulk_logged all the time, then any old SELECT INTO, small index creation, data load can result in you lose ability to:&lt;/p&gt;
&lt;p&gt;1) restore the following log backup to point in time.&lt;/p&gt;
&lt;p&gt;2) produce the following log backup in case data file is corrupt somehow.&lt;/p&gt;
&lt;p&gt;I prefer to stay on top of above points and only switch down to bulk_logged when I really want this.&lt;/p&gt;
</description></item><item><title>re: Bulk logged recovery model and log backups</title><link>http://sqlblog.com/blogs/tibor_karaszi/archive/2007/08/19/bulk-logged-recovery-model-and-log-backups.aspx#15238</link><pubDate>Mon, 13 Jul 2009 13:06:28 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:15238</guid><dc:creator>Blackhawk</dc:creator><description>&lt;p&gt;Thank you.&lt;/p&gt;
&lt;p&gt;Clearest answer I have had to this question so far.&lt;/p&gt;
&lt;p&gt;The index creation component really brought the whole thing to light.&lt;/p&gt;
&lt;p&gt;Regards;&lt;/p&gt;
&lt;p&gt;BlackHawk&lt;/p&gt;
</description></item></channel></rss>