--- In firebird-support@yahoogroups.com, "Svein Erling"
<svein.erling.tysvaer@k...> wrote:

> --- In firebird-support@yahoogroups.com, "Martijn Tonies" wrote:
> > To automatically tell which plans would change is a no-go. I

cannot

> > create something like that.
> >
> > Perhaps, storing queries and their plans for later comparison

would

> > be possible.
> >
> > It already has quite a visual PLAN Analyzer - see:
> > http://www.upscene.com/documentation/dbw/oe_sqleditor.htm
>
> I was just thinking about his current problem: "What would happen

to

> my system with 100s of queries if I added an index?" If those

queries

> were stored somewhere together (in a different table) with their
> plans, then it should be easy to write a piece of code that after
> creation of the index could tell which plans were different and

needed

> further investigation using the Plan Analyzer. Though I do not know
> whether this should be part of Firebird Workbench or a separate

tool.

> Possibly both, a simple, clumsy freeware version written in a few
> hours one afternoon and then a more sophisticated "Tonies gold"
> version suitable for those who just want things to work quickly in

an

> intuitive manner.
>
> Set

I would have thought that the process of deciding which indexes to
use would be something that would have been sorted out in the days of
beta. I imagine that if I ran the same situation in another engine,
it might not happen. Surely it can not be passed off as just a
standard issue.
I think that the idea of having a table full of queries is not a
bad idea and it is easy to run them with the index on and then off.
The difficult part for us is that almost all of the queries are build
from c++ code based on criteria and what not so it would be difficult
to manage.
I hope one of the developers looks into it because the case I have
given shows it up perfectly and we have been pressured a bit by our
client to use that Microsoft thing which goes against my principles.