I have read some articles abouit it.
if you have high update/insert oltp applicatioin use 70-80% for fill factor.
But I always say it depends on particular situation/query/business
requirements and you have to test by yourself.
> Created a clustered index and nonclustered indexes on a
> table with 5,953,675 rows using a fillfactor of "95" for
> clustered index and "98" for nonclustered indexes.
> After 82,119 inserts (.01 of table), the nonclustered
> indexes had a value of "83" for scan density, "4" for
> logical frag, and "96" for avg. page density. The
> clustered index had a value of "96" for scan density, "1"
> for logical frag, and "88" for avg. page density.
> Methinks I should have used a fillfactor for the
> nonclustered indexes a value of "96", and a fillfactor
> value of "96" for the clustered index. The table and
> indexes span multiple files. Confused on trade-off on
> scan density versus avg. page density with nightly inserts.
> Am in an OLAP (Data Warehouse) environment. Have other
> tables with similiar scenarios (roughly one percent of
> table being done nightly with inserts).
> Am open to anything. Thank you
I have a SQL server 6.5 installation.
One of the tables has an average page density of 55%.
How can I increase the average page density of this table.
Table's row size is around 252 bytes.
It has 1.3 million records.
I tried reindexing, and dropping and recreating index.
3. Scan Density