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

>
> Sometimes it is good to use an index, sometimes not. You have to figure
> out how the indexes are used, not just look at indexed reads being used.
> Moreover, if you run several slow queries simultaneously, it will affect
> other queries as well. One possible 'solution', is in some cases to use
> Classic Server rather than SuperServer, but that only helps in that
> simultaneous queries from different users may use different processors
> rather than compete for the same resources.

I tried Classic server. It was the same.

>
> Most of us do not think Firebird is slow, although I have no problems
> admitting that the PLAN Firebird chooses sometimes isn't good so that
> some tweaking is needed.

Some of the queries I use, are not changed from a long time. And with 2.0.x they worked fine.

> Other than that, well, I can only think of
> issues like having .gdb filename extension (formerly, that was the
> normal extension for InterBase databases) on certain Windows versions
> makes the operating system take a backup upon connect.

I use FDB file extension since version 1.5
Of course, it is

> not difficult to write lousy queries that takes forever, but your
> particular query doesn't seem too bad (the only thing I noticed was that
> you used indexed reads to access all records in PARTIDA_NAL), although
> the PLAN is a key point that you haven't told us anything about.
> Set

We celebrating Easter right now and I can give you the PLAN on Tuesday.