Subject | Re: [ib-support] Assure me |
---|---|
Author | Ann W. Harrison |
Post date | 2003-01-13T16:40:16Z |
At 12:48 PM 1/13/2003 +0100, Pete Clark wrote:
If your data is archival, then non-selective indexes aren't a great
problem. If you delete rows or change the value of the indexed
field, non-selective indexes introduce performance problems with
garbage collection.
Regards,
Ann
www.ibphoenix.com
We have answers.
> >The number of indexes is not all too important, what matters is theirLike so many things, the appropriate selectivity depends on usage.
> >selectivity.
>Is there some sort of way of figuring out what the 'boundary' is?
>
>Like, a spread of 50% ( a boolean field ) is obviously silly. But what
>sort of percentage should I drop to, before actually creating an index?
If your data is archival, then non-selective indexes aren't a great
problem. If you delete rows or change the value of the indexed
field, non-selective indexes introduce performance problems with
garbage collection.
Regards,
Ann
www.ibphoenix.com
We have answers.