Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Default Index Fill Factor


Default Index Fill Factor

Author
Message
Nadrek
Nadrek
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1029 Visits: 2673
SQLRNNR (4/2/2010)

No single default fill factor is appropriate for all indexes. It should be evaluated case by case.


True; but it's our job as administrators to deliberate on the best default, which will kick in when someone creates an index and does not evaluate their particular case! Not uncommon in smaller shops.

The default is 0, which translates to 100%. In my area, the idea of a 100% fill factor as a default is... substandard. More often than not in my area, an index is not on columns that are continually increasing and never changed; it's on data that is either inserted in nonindex (usually arbitrary) order, or is updated regularly. In both of these cases, a 100% fill factor results in quick fragmentation, and the index taking up more space than it would have at a smaller fill factor.

How much below 100% as a default, though... that's a much, much more difficult question. For large tables with non-repeating but arbitrarily ordered data (person or object or paperwork ID numbers out of its home tables, etc.), a high fill factor is fine; you're going to be doing a few inserts/changes to a large number of scattered changes, and even a little bit of space free prevents the vast majority of page splits... unless you have queries that operate on clusters of index columns.
philvarney
philvarney
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 12
a few years old now- but I was wondering the same. 100 means 100% but what 0 meant I think has changed. Certainly back in the early Sybase days I think that 0 meant (something like) 100% for clustered, 80% for non-clustered (or the other way around) - this was something "built in" as a default. Not sure if SQL Server was the same and/or if Sybase has now changed it, but I guess that's the core of the original posters question and something I was wondering myself...
bdefreitas
bdefreitas
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 128
I used to think the default Fill Factor was 80%. But I believe I thought that because I used to use Erwin heavily back then, and I THINK their default was 80% FF (or we set it that way for Erwin default FF)....



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search