Re: Fill Factor
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Sun, 17 Feb 2008 08:50:47 -0500
My guess would be that someone set up a maintenance plan that reindexes the tables and has the fill factor set to 90 there. But why would this cause problems? I would think it would eliminate more problems than it would cause. Having the fill factor at 0 means that each leaf level is essentially 100% full and any additional insert or update with more bytes than before will cause a page split. With a Fill Factor of 90 you at least have some room to operate and still minimize page splits.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Saeed Abd Al-Ati" <SaeedAbdAlAti@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:92FA67B7-FAAC-4F74-9F3D-4F4CEEB81DF4@xxxxxxxxxxxxxxxx
Hi,
I am facing a Weird problem in configuring the Fill Factor for my production
database, i deployed a database to a client and sit the Fill Factor for all
indexes to be "0" which is the default value, after 1 week the value changed
to be "90" which caused some problems in the application, since there are
some problems in HD allocations, my question is: how this value changed
automatically? taking into consideration that there is no specific
devleopment/administration script applied on the Database.
Thanks in advance.
.
- Follow-Ups:
- Re: Fill Factor
- From: Saeed Abd Al-Ati
- Re: Fill Factor
- From: Saeed Abd Al-Ati
- Re: Fill Factor
- Prev by Date: Re: Slipstream SQL 2005 SP2
- Next by Date: SQL user log on every 30 mins?
- Previous by thread: Slipstream SQL 2005 SP2
- Next by thread: Re: Fill Factor
- Index(es):
Relevant Pages
|