<?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>Index Rebuild vs Reorganize:  The transaction log edition</title><link>http://blogs.msdn.com/b/timchapman/archive/2012/09/28/index-rebuild-vs-reorganize-the-transaction-log-edition.aspx</link><description>Recently a friend and fellow PFE Dave Levy ( Twitter / Blog ) and I were discussing a question someone posted in a forum. The question was in regards to database mirroring latency when a reorganization occurs. Dave mentioned that he has seen in the past</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Index Rebuild vs Reorganize:  The transaction log edition</title><link>http://blogs.msdn.com/b/timchapman/archive/2012/09/28/index-rebuild-vs-reorganize-the-transaction-log-edition.aspx#10371950</link><pubDate>Tue, 27 Nov 2012 06:52:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10371950</guid><dc:creator>patrick</dc:creator><description>&lt;p&gt;For &amp;nbsp;defragmentation of sql server we can also use a specific tool this will save our time also ..this will give a complete report for your server performance related activitis where we can monitor all transaction log also &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10371950" width="1" height="1"&gt;</description></item><item><title>re: Index Rebuild vs Reorganize:  The transaction log edition</title><link>http://blogs.msdn.com/b/timchapman/archive/2012/09/28/index-rebuild-vs-reorganize-the-transaction-log-edition.aspx#10356234</link><pubDate>Fri, 05 Oct 2012 04:30:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10356234</guid><dc:creator>ram</dc:creator><description>&lt;p&gt;We are seeing otherwise. Reorganize generates large amount of logs on a table that is 5% fragmented and 100 GB in size.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10356234" width="1" height="1"&gt;</description></item><item><title>re: Index Rebuild vs Reorganize:  The transaction log edition</title><link>http://blogs.msdn.com/b/timchapman/archive/2012/09/28/index-rebuild-vs-reorganize-the-transaction-log-edition.aspx#10354229</link><pubDate>Fri, 28 Sep 2012 17:24:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10354229</guid><dc:creator>TimChapman</dc:creator><description>&lt;p&gt;Thanks Paul, and I completely agree. &amp;nbsp;In this post I was going for a completely fragmented index, but I&amp;#39;ll add some info regarding what you said. &amp;nbsp;I don&amp;#39;t want people to make decisions based just on the log generation rate.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10354229" width="1" height="1"&gt;</description></item><item><title>re: Index Rebuild vs Reorganize:  The transaction log edition</title><link>http://blogs.msdn.com/b/timchapman/archive/2012/09/28/index-rebuild-vs-reorganize-the-transaction-log-edition.aspx#10354224</link><pubDate>Fri, 28 Sep 2012 17:12:16 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10354224</guid><dc:creator>Paul Randal</dc:creator><description>&lt;p&gt;What was the fragmentation level of the index before each operation? Remember that a reorganize is not efficient for a heavily fragmented index - by design. You need to consider the fragmentation because the rebuild will *always* generate a new index, with all those log records, but for a low-fragmented index, the reorganize will hardly generate any.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10354224" width="1" height="1"&gt;</description></item></channel></rss>