<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SQL SERVER &#8211; Fillfactor, Index and In-depth Look at Effect on Performance</title>
	<atom:link href="http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/</link>
	<description>Personal Notes of Pinal Dave</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:45:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SQL SERVER &#8211; Correct Value for Fillfactor &#8211; Quiz &#8211; Puzzle &#8211; 24 of 31 &#171; SQL Server Journey with SQL Authority</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-243206</link>
		<dc:creator><![CDATA[SQL SERVER &#8211; Correct Value for Fillfactor &#8211; Quiz &#8211; Puzzle &#8211; 24 of 31 &#171; SQL Server Journey with SQL Authority]]></dc:creator>
		<pubDate>Wed, 25 Jan 2012 01:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-243206</guid>
		<description><![CDATA[[...] SQL SERVER – What is Fill Factor and What is the Best Value for Fill Factor Fillfactor, Index and In-depth Look at Effect on Performance Rebuild Every Index of All Tables of Database – Rebuild Index with FillFactor Change Default Fill [...]]]></description>
		<content:encoded><![CDATA[<p>[...] SQL SERVER – What is Fill Factor and What is the Best Value for Fill Factor Fillfactor, Index and In-depth Look at Effect on Performance Rebuild Every Index of All Tables of Database – Rebuild Index with FillFactor Change Default Fill [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kasib</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-222508</link>
		<dc:creator><![CDATA[Kasib]]></dc:creator>
		<pubDate>Wed, 21 Dec 2011 01:41:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-222508</guid>
		<description><![CDATA[Hey, I am in the process of preparing for 70-450 exam and I came across this question on the net. I eliminated the two answers, B,C. Index is performing fine, so no need to rebuild or reorganize. Can you please help.

QUESTION::::
You are designing index maintenance strategies.  One large table has a clustered index which never has a fragmentation percentage of more than 2 percent.  There is an XML column in the table, and INSERTs are run frequently against this table.  You want to minimize the impact of reindexing operations on performance.
 
A) Drop the clustered index on the large table.
 B) Rebuild the clustered index of the large table monthly.
 C) Exclude the clustered index from reorganizing and rebuilding.
 D) Reduce the fillfactor on the clustered index.]]></description>
		<content:encoded><![CDATA[<p>Hey, I am in the process of preparing for 70-450 exam and I came across this question on the net. I eliminated the two answers, B,C. Index is performing fine, so no need to rebuild or reorganize. Can you please help.</p>
<p>QUESTION::::<br />
You are designing index maintenance strategies.  One large table has a clustered index which never has a fragmentation percentage of more than 2 percent.  There is an XML column in the table, and INSERTs are run frequently against this table.  You want to minimize the impact of reindexing operations on performance.</p>
<p>A) Drop the clustered index on the large table.<br />
 B) Rebuild the clustered index of the large table monthly.<br />
 C) Exclude the clustered index from reorganizing and rebuilding.<br />
 D) Reduce the fillfactor on the clustered index.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 20 of 31 Journey to SQLAuthority</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-149458</link>
		<dc:creator><![CDATA[SQL SERVER – Interview Questions and Answers – Frequently Asked Questions – Day 20 of 31 Journey to SQLAuthority]]></dc:creator>
		<pubDate>Wed, 20 Jul 2011 01:31:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-149458</guid>
		<description><![CDATA[[...] Specifying a fill-factor value of 70 would imply that 30 percent of each page will be left empty, providing space for index expansion as data is added to the underlying table. The fill-factor setting applies only when the index is created or rebuilt. (Read more here) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Specifying a fill-factor value of 70 would imply that 30 percent of each page will be left empty, providing space for index expansion as data is added to the underlying table. The fill-factor setting applies only when the index is created or rebuilt. (Read more here) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kuldip.Bhatt</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58899</link>
		<dc:creator><![CDATA[Kuldip.Bhatt]]></dc:creator>
		<pubDate>Tue, 22 Dec 2009 10:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58899</guid>
		<description><![CDATA[very nice explanation and all the comments are very good.]]></description>
		<content:encoded><![CDATA[<p>very nice explanation and all the comments are very good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58847</link>
		<dc:creator><![CDATA[Pinal Dave]]></dc:creator>
		<pubDate>Sun, 20 Dec 2009 13:35:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58847</guid>
		<description><![CDATA[Hello Srinivas,

Yes, when free space specified by fillfactor, fills after few insertion, page split wll occure. The benifit of fillfactor is to allow insert/update until the free space not filled. The free space specified by fill factor is reserved everytime the index is rebuild or defragmented. So we just have to plan a proper schedule to degrag/rebuild the indexes to maintain the free space and to avoid the page split.

Kind Regards,
Pinal Dave]]></description>
		<content:encoded><![CDATA[<p>Hello Srinivas,</p>
<p>Yes, when free space specified by fillfactor, fills after few insertion, page split wll occure. The benifit of fillfactor is to allow insert/update until the free space not filled. The free space specified by fill factor is reserved everytime the index is rebuild or defragmented. So we just have to plan a proper schedule to degrag/rebuild the indexes to maintain the free space and to avoid the page split.</p>
<p>Kind Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Srinivas</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58790</link>
		<dc:creator><![CDATA[Srinivas]]></dc:creator>
		<pubDate>Fri, 18 Dec 2009 07:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58790</guid>
		<description><![CDATA[Hi Pinal,

Nice Post.

But, I have a question here. In order to avoid page splits we use fill factor. If we don&#039;t specify fill factor on a table, inorder to accommodate a new record page split happens, and while page split happening, it moves half of the page to another page and this is costly.

Lets say if i have mentioned as fillfactor 80, means it will reserve 20% of every page for new records. what if this 20% of space also filled with new records, what will happen at that time?

If it results in a page split, what is the difference of having a page split at the insertion or very first record or after sometime?

Please answer my question...]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>Nice Post.</p>
<p>But, I have a question here. In order to avoid page splits we use fill factor. If we don&#8217;t specify fill factor on a table, inorder to accommodate a new record page split happens, and while page split happening, it moves half of the page to another page and this is costly.</p>
<p>Lets say if i have mentioned as fillfactor 80, means it will reserve 20% of every page for new records. what if this 20% of space also filled with new records, what will happen at that time?</p>
<p>If it results in a page split, what is the difference of having a page split at the insertion or very first record or after sometime?</p>
<p>Please answer my question&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chrystal</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58779</link>
		<dc:creator><![CDATA[Chrystal]]></dc:creator>
		<pubDate>Thu, 17 Dec 2009 21:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58779</guid>
		<description><![CDATA[Pinal,That is very clear explanation.  before I never know why we care about fillfactor. I &#039;ve always used your site for help. Thank you so much for your all very awesome articles.]]></description>
		<content:encoded><![CDATA[<p>Pinal,That is very clear explanation.  before I never know why we care about fillfactor. I &#8216;ve always used your site for help. Thank you so much for your all very awesome articles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rama</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58752</link>
		<dc:creator><![CDATA[Rama]]></dc:creator>
		<pubDate>Thu, 17 Dec 2009 09:58:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58752</guid>
		<description><![CDATA[Hi Pinal,

You have nicely summerised a complicated as well as important subject.

Rama]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal,</p>
<p>You have nicely summerised a complicated as well as important subject.</p>
<p>Rama</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pinal Dave</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58738</link>
		<dc:creator><![CDATA[Pinal Dave]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 20:02:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58738</guid>
		<description><![CDATA[Hello Laerte,

Yes, a fillfactor to 100 for any table that can be updated would definately cause page split issue. FillFactor 100 is only suitable for read-only tables.
Thank you.

Regards,
Pinal Dave]]></description>
		<content:encoded><![CDATA[<p>Hello Laerte,</p>
<p>Yes, a fillfactor to 100 for any table that can be updated would definately cause page split issue. FillFactor 100 is only suitable for read-only tables.<br />
Thank you.</p>
<p>Regards,<br />
Pinal Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramdas</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58725</link>
		<dc:creator><![CDATA[Ramdas]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 15:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58725</guid>
		<description><![CDATA[Nice tip on the fill factor for inserting rows with columns as identity. It is a key parameter to keep in mind while designing databases.]]></description>
		<content:encoded><![CDATA[<p>Nice tip on the fill factor for inserting rows with columns as identity. It is a key parameter to keep in mind while designing databases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kapil Bhargava</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58714</link>
		<dc:creator><![CDATA[kapil Bhargava]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 11:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58714</guid>
		<description><![CDATA[It proved to be very informative]]></description>
		<content:encoded><![CDATA[<p>It proved to be very informative</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kapil</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58713</link>
		<dc:creator><![CDATA[kapil]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 11:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58713</guid>
		<description><![CDATA[Thanks for this post. this is very informative]]></description>
		<content:encoded><![CDATA[<p>Thanks for this post. this is very informative</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suhas</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58700</link>
		<dc:creator><![CDATA[Suhas]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 06:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58700</guid>
		<description><![CDATA[Nice One
Thanks for the explanation

Suhas]]></description>
		<content:encoded><![CDATA[<p>Nice One<br />
Thanks for the explanation</p>
<p>Suhas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ritesh Shah</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58691</link>
		<dc:creator><![CDATA[Ritesh Shah]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 05:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58691</guid>
		<description><![CDATA[You read my mind Sir, I was thinking to dig almost this topic but time doesn&#039;t permit me. thank you very much for this great post. :)]]></description>
		<content:encoded><![CDATA[<p>You read my mind Sir, I was thinking to dig almost this topic but time doesn&#8217;t permit me. thank you very much for this great post. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laerte Junior</title>
		<link>http://blog.sqlauthority.com/2009/12/16/sql-server-fillfactor-index-and-in-depth-look-at-effect-on-performance/#comment-58683</link>
		<dc:creator><![CDATA[Laerte Junior]]></dc:creator>
		<pubDate>Wed, 16 Dec 2009 02:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sqlauthority.com/?p=7561#comment-58683</guid>
		<description><![CDATA[Hi Pinal, Great Post. I totally agree &quot;if the index key column is an IDENTITY column, the key for new rows is always increasing and the index rows are logically added to the end of the index&quot;
I just believe there is not a rule to say that the if index key column is an IDENTITY column, you can configure the fillfactor with 100%
Even if you have index key column is an IDENTITY and configuring fillfactor to 100% if you have variable-length columns (varchar, nvarchar, varbinay) and they suffer constant change or change more than insertion, you will probably have problems with page splits . In these cases perhaps, even though the identity column, leaving a smaller fillfactor may be more appropriate.]]></description>
		<content:encoded><![CDATA[<p>Hi Pinal, Great Post. I totally agree &#8220;if the index key column is an IDENTITY column, the key for new rows is always increasing and the index rows are logically added to the end of the index&#8221;<br />
I just believe there is not a rule to say that the if index key column is an IDENTITY column, you can configure the fillfactor with 100%<br />
Even if you have index key column is an IDENTITY and configuring fillfactor to 100% if you have variable-length columns (varchar, nvarchar, varbinay) and they suffer constant change or change more than insertion, you will probably have problems with page splits . In these cases perhaps, even though the identity column, leaving a smaller fillfactor may be more appropriate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

