Subject | Re: Re: [ib-support] Progress on making queries run faster |
---|---|
Author | gkrishna@jlmatrix.com |
Post date | 2003-04-04T13:35:08Z |
What we do is have a process which we call "housekeeping" which we run every 15 days or one month.
We dont give the user a choice. Unless housekeeping is done at least once a month, the application will not run.
We take everybody offline.
Do a backup and a restore.
Advantages -
Indexes are recreated
Though we recommend daily backup we know users often dont do this so at least you have a backup at worst one month old.
So unless yours is 24 x 7 application. This kills two birds with one stone.
One month is OK for that app. You decide what it is for your app.
GK
Pavel Cisar wrote:
I hope this will become unnecessary in 2.0
Regards,
Mark
We dont give the user a choice. Unless housekeeping is done at least once a month, the application will not run.
We take everybody offline.
Do a backup and a restore.
Advantages -
Indexes are recreated
Though we recommend daily backup we know users often dont do this so at least you have a backup at worst one month old.
So unless yours is 24 x 7 application. This kills two birds with one stone.
One month is OK for that app. You decide what it is for your app.
GK
Pavel Cisar wrote:
> It's normal :-) You don't need to drop and recreate, just use ALTER INDEXThanks for the reply. I expect our users will be happier every 30% changed.
> INACTIVE and then ALTER INDEX ACTIVE for the same effect.
>
> Why the performance is better after that:
>
I hope this will become unnecessary in 2.0
Regards,
Mark