brother_of_karamazov
Legendary Poster
Okay, the "Naked Women" portion was just to get you to look at my post. Pathetic but it worked now didn't it?
E1 ships with a default fill factor for SQL Server of '0', which basically means that each leaf level page is filled to capacity and leaves no room for additional rows without the need for page splitting. While a fill factor of 0 is an efficient use of page space I think it sucks as a default value.
Questions:
Does anyone know how to change the default fill factor in E1 so that, if I change the fill factor in SQL, the old fill factor is not re-introduced if the index is regenerated within E1? I would like to change the fill factor to something I think is more reasonable but would like to not have that value overridden by E1 if an index is regenned.
I suppose I could set up a maintenance plan in SQL to rebuild the indexes weekly and use the fill factor I desire so even if someone does regen the index, at the end of the week it will be rebuilt with my fill factor and not the E1 default.
Thoughts?
E1 ships with a default fill factor for SQL Server of '0', which basically means that each leaf level page is filled to capacity and leaves no room for additional rows without the need for page splitting. While a fill factor of 0 is an efficient use of page space I think it sucks as a default value.
Questions:
Does anyone know how to change the default fill factor in E1 so that, if I change the fill factor in SQL, the old fill factor is not re-introduced if the index is regenerated within E1? I would like to change the fill factor to something I think is more reasonable but would like to not have that value overridden by E1 if an index is regenned.
I suppose I could set up a maintenance plan in SQL to rebuild the indexes weekly and use the fill factor I desire so even if someone does regen the index, at the end of the week it will be rebuilt with my fill factor and not the E1 default.
Thoughts?