Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Hariarul
Posting Yak Master
160 Posts |
 Posted - 2007-08-16 : 02:01:54
|
| Hi all,We have a database that has few tables which are very huge with over 200 million records. Mostly the data is retrieved by the application with minimal data insertion. We have left the fill factor as default for now. Should I set a explicit value for the fill factor of the indexes in the huge tables ?If Yes, what ways it would help us ?Thanks & Regards,Hariarul |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2007-08-16 : 06:15:47
|
| if you have ah identity or similar ever growing PK then you can set the fill factor to 100%.larger fill factor means more data in each page which means less reads to get same data which means less IO reads which meansshorter execution time_______________________________________________Causing trouble since 1980blog: http://weblogs.sqlteam.com/mladenp |
 |
|
|
pootle_flump
1064 Posts |
Posted - 2007-08-16 : 09:42:44
|
| Although that only applies at the time of index creation\ rebuild. The downside is more densly populated data\ index pages are more prone to page splits on inserts and updates (increasing the length of variable length columns). As Spirit says, there will be no page splits on insert into ever increasing indexes (clustered or otherwise). However if your data changes regularly and rows often grow then you need to consider this. Read BoL for more details. Also check PAD_INDEX too. |
|
|
|
|
|
|
Fill factor ;