It has nothing to do with normalization, store_no is part of a 2
field primary key.

But instead of wondering why another database can handle these types
of queries so fast and Firebird can't, and what we can do to
possible make Firebird run better in these situations, you want to
try to belittle the person that is looking for answers.

I'm trying to become a potentially large customer of IBPhoenix and
the only way that can happen is if Firebird can at "least" do what
my current database can do.

Try to help the progress, not hender it with remarks that you are
not thinking clear about.

Thanks

--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> > >I cannot understand why anyone would
> > > want to run a statement without a where clause on a million-row
> > table
> > > (well, possibly if there were some kind of grouping reducing

the

> > > returned set to a few rows)
> >
> > My query does only return a few records from the table, I'm using
> > a 'distinct' clause.
> >
>
> so you want to scan 2.1 million records to pull back 5 distinct

occurrences

> (handfull)? and you're holding the index efficiency as responsible

for poor

> timing?
> Seems to me that a bit of normalising of your data is on order no?
> Alan