Hi Set,

> The problem is obviously that Firebird thinks it can do a better job
> if it uses this new index for this particular query. I can think of
> two ways to solve your problem, the best being to create a small
> program which prepare all your queries and reports if any of them have
> changed plan since last time you ran the program. That way you would
> at least know which queries to examine rather than have to manually
> check all of them.
>
> Thinking about it, that could be a nice addition to Database WorkBench
> (to tell which queries will change plan with the addition/removal of
> indexes). Or maybe you've got something like that already, Martijn (or
> is it beyond the purpose of Workbench)?

Eh... dunno. :-)

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

(scroll down to bottom)


With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird & MS SQL Server.
Upscene Productions
http://www.upscene.com