You are correct that some indexes on system tables can get lost in a backup
and restore. What I advise you to do is to check for a named index at some
convenient time with your application and if it isn't there to go ahead and
create it. It appears to me there isn't anything I can do to optimize a
query that has no index on it. I could perhaps pull in all the data and
sort it in memory too. I'll add this to my list of development items to
work on but I'm convinced there will be something you can do in your
application to safeguard against this.

Kind regards,
Jason Wharton
www.ibobjects.com

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Enrico Raviglione
> Sent: Wednesday, June 01, 2005 7:32 AM
> To: IBObjects@yahoogroups.com
> Subject: RE: [IBO] for Jason: TIBOQuery vs. TFIBDataset speed test
>
>
> Hi Jason,
>
> what kind of index we must add to our database, an Index on system
> tables ?
> But this kind of operation are not discouraged ?
> I don't remeber why but during the transition fron FireBird 1.0.x to
> 1.5.x i have readed that the index on the system table are
> lost in some
> circustances, backup -> restore or some other.
>
> Do you think to change your query and optimize it in next
> version of IBO
> ? and when ?
>
> Best Regards.
>
> Enrico Raviglione
>
> IDEA Sistemi s.n.c.
> Via Burolo, 30
> 10015 IVREA ( TO )
> ITALY
> TEL. +39 0125 253235
> FAX +39 0125 253271
> www.ideasistemi.it
> e.raviglione@...
>
> > -----Original Message-----
> > From: IBObjects@yahoogroups.com
> > [mailto:IBObjects@yahoogroups.com] On Behalf Of Jason Wharton
> > Sent: Wednesday, June 01, 2005 4:05 PM
> > To: 'IBObjects@yahoogroups.com'
> > Subject: RE: [IBO] for Jason: TIBOQuery vs. TFIBDataset speed test
> >
> > I always suggest people look at the performance monitor/SQL
> > trace because the query requesting that information may not
> > be working optimally and the addition of an index on the
> > server could greatly increase the performance if there is a
> > lot of data in the system tables. Watching the SQL trace
> > will reveal where the time lag is at.
> >
> > Jason Wharton
> > www.ibobjects.com