<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Index Fragmentation Findings: Part 2, Size Matters</title>
	<atom:link href="http://www.brentozar.com/archive/2009/02/index-fragmentation-findings-part-2-size-matters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brentozar.com/archive/2009/02/index-fragmentation-findings-part-2-size-matters/</link>
	<description>Your technology pain-relief experts.</description>
	<lastBuildDate>Wed, 08 Feb 2012 16:37:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Brent Ozar</title>
		<link>http://www.brentozar.com/archive/2009/02/index-fragmentation-findings-part-2-size-matters/comment-page-1/#comment-8861</link>
		<dc:creator>Brent Ozar</dc:creator>
		<pubDate>Fri, 15 May 2009 15:20:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2458#comment-8861</guid>
		<description>Jonathan - everything is &quot;Your mileage may vary.&quot;  Depends on the random speed of the drives, the read vs write mix of the data, the frequency that the data is queried, etc.  My approach is to start with Michelle Ufford&#039;s excellent index defrag script, set it with very high thresholds (like only rebuild indexes when things are extremely fragmented) and then see how long it takes to run.  Then I turn it down lower and lower over time so that I defrag as much as possible in as little time as possible.  Whatever performance gains I can get from it, great, but I don&#039;t go to the individual table to look at fragmentation vs size vs read/write mix and so on.</description>
		<content:encoded><![CDATA[<p>Jonathan &#8211; everything is &#8220;Your mileage may vary.&#8221;  Depends on the random speed of the drives, the read vs write mix of the data, the frequency that the data is queried, etc.  My approach is to start with Michelle Ufford&#8217;s excellent index defrag script, set it with very high thresholds (like only rebuild indexes when things are extremely fragmented) and then see how long it takes to run.  Then I turn it down lower and lower over time so that I defrag as much as possible in as little time as possible.  Whatever performance gains I can get from it, great, but I don&#8217;t go to the individual table to look at fragmentation vs size vs read/write mix and so on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonathanA</title>
		<link>http://www.brentozar.com/archive/2009/02/index-fragmentation-findings-part-2-size-matters/comment-page-1/#comment-8846</link>
		<dc:creator>JonathanA</dc:creator>
		<pubDate>Fri, 15 May 2009 11:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2458#comment-8846</guid>
		<description>Brent, does this scale down at all?

I have 3 productions servers. Only one database has indexes that are over 10000 pages, only 3 others have indexes over 1000 pages.

I have scheduled jobs that defrag indexes on the main databases (HR, Accounts, CRM etc) as I know they cause slowdowns if they are not kept neat and tidy.

Doesnt the frag %age have a vote in whether the index should be rebuilt/reorganised? Or does a 500 page index that is 90% fragged not cause the problems that a 5000 page index that is 2% fragged ...

Jonathan</description>
		<content:encoded><![CDATA[<p>Brent, does this scale down at all?</p>
<p>I have 3 productions servers. Only one database has indexes that are over 10000 pages, only 3 others have indexes over 1000 pages.</p>
<p>I have scheduled jobs that defrag indexes on the main databases (HR, Accounts, CRM etc) as I know they cause slowdowns if they are not kept neat and tidy.</p>
<p>Doesnt the frag %age have a vote in whether the index should be rebuilt/reorganised? Or does a 500 page index that is 90% fragged not cause the problems that a 5000 page index that is 2% fragged &#8230;</p>
<p>Jonathan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott R.</title>
		<link>http://www.brentozar.com/archive/2009/02/index-fragmentation-findings-part-2-size-matters/comment-page-1/#comment-7321</link>
		<dc:creator>Scott R.</dc:creator>
		<pubDate>Thu, 12 Feb 2009 09:07:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.brentozar.com/?p=2458#comment-7321</guid>
		<description>Brent, 
 
Great post and series!  Looking forward to part 3. 
 
The small / medium / large categories helps put priority and focus where it is needed most - kind of like &quot;don&#039;t waste your time&quot; / &quot;look a little closer&quot; / &quot;really pay attention!&quot;. 
 
While I understand the stated index size thresholds of 10,000 pages and 50,000 pages (and that page count is the metric which was collected), it may also be helpful to offer a relative perspective by stating these thresholds for reference purposes as storage capacity metrics of about 80 MB (10,000 pages x 8 KB page size) and about 400 MB (50,000 pages x 8 KB page size).  The &quot;about&quot; caveat depends on whether your preferred storage metric unit measures are decimal (MB  = 1,000,000 bytes or 10^6 bytes) or binary (MB = 1,048,576 bytes or  2^20 bytes) - roughly a 5% difference for MB and 7.3% for GB. 
 
Scott R. </description>
		<content:encoded><![CDATA[<p>Brent, </p>
<p>Great post and series!  Looking forward to part 3. </p>
<p>The small / medium / large categories helps put priority and focus where it is needed most &#8211; kind of like &quot;don&#039;t waste your time&quot; / &quot;look a little closer&quot; / &quot;really pay attention!&quot;. </p>
<p>While I understand the stated index size thresholds of 10,000 pages and 50,000 pages (and that page count is the metric which was collected), it may also be helpful to offer a relative perspective by stating these thresholds for reference purposes as storage capacity metrics of about 80 MB (10,000 pages x 8 KB page size) and about 400 MB (50,000 pages x 8 KB page size).  The &quot;about&quot; caveat depends on whether your preferred storage metric unit measures are decimal (MB  = 1,000,000 bytes or 10^6 bytes) or binary (MB = 1,048,576 bytes or  2^20 bytes) &#8211; roughly a 5% difference for MB and 7.3% for GB. </p>
<p>Scott R.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Object Caching 519/523 objects using disk: basic

Served from: www.brentozar.com @ 2012-02-09 07:15:29 -->
