Posted by smithabreddy on 06/09/06 17:05

Fill Factor - please look this up in Books online.

-------
>From BOL:
The fill factor option is provided for fine-tuning index data storage
and performance. When an index is created or rebuilt, the fill factor
value determines the percentage of space on each leaf level page to be
filled with data, therefore reserving a percentage of free space for
future growth. For example, specifying a fill factor value of 80 means
that 20 percent of each leaf-level page will be left empty providing
space for index expansion as data is added to the underlying table.

The fill factor value is a percentage from 1 to 100. The server-wide
default of 0 is the optimal choice in the majority of situations. When
fill factor is set to 0, the leaf level is filled almost to capacity,
but some space remains for at least one additional index row. With this
setting, the leaf level space is used efficiently, but room remains for
limited expansion before the page must be split.

Note:
Fill factor values 0 and 100 are the same in all respects.
-------

Not sure why the fragmentation still shows the same. After the
rebuild, can you run the following and the the first SELECT query again
see if the fragmentation has changed? (This is a very resource
intensive operation).

UPDATE STATISTICS Customers WITH FULLSCAN

wackyphill@yahoo.com wrote:
> The Fill_factor is 0 on all my indexes, however I must admit I don't
> know what fill factor really means.

[Back to original message]