I inactivated all triggers because I thought something there was
causing this. Same thing happens!!!

I get the same results with QuickDesk and with Marathon. The first
time I run the SQL (after a reboot) it takes approx. 2.5 seconds to
run. After the first time it is almost instantaneous. I get the
23,000 non indexed reads each time I run the SQL (not just the first
time).

I noticed this because I have had to run a few stored procedures to
update some data and the updates were taking forever.

My worry is that things are taking along time because I have so many
Foreign Keys defined (some with cascade update and delete and some
without). This is a fairly large and complicated database. I am
thinking about removing all Foreign Keys and replacing them with
triggers but this is going to be quite onerous.

Todd

--- In ib-support@y..., "Jason Wharton" <jwharton@i...> wrote:
> > I suspect this is a bug/anomaly of Marathon, please try the statement
> > from ISQL and report it's results.
>
> He might have some triggers doing things. Or, it could be the
problem of the
> profiler they are using. (Mine?)
>
> How long does the operation take on a stop watch?
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com