Hi Todd,

Lots of things come into play here.

The first thing I would check is how long it takes to execute the
select query with no inserts.

Is there a better way of achieving this? For example, could you use a
trigger to fill the other table as the changes are made. You have
mentioned there are no stored procedures or triggers that are run on
the insert events which I would have totally forgotten to check
(oops). What about indices (or indexes, shudder). Do you have any
that would need to be updated that may be slowing the process down?

Is the performance any better if you use an 'insert into tableb
select * from tablea' type query?

Just some ideas for you to consider, still 166 inserts per second
isn't that slow. What hardware are you running this on?

Adam

--- In firebird-support@yahoogroups.com, "Todd Pinel"
<todd_pinel@y...> wrote:

> Hi I was wondering what kind of performance is normal to expect when
> inserting multiple records into Firebird? The scenario I have

right now is

> I call a stored procedure that runs a For..Select to gather a list

of people

> that need to be inserted into another table. This query is simple

basically

> select all people with this attribute. I have in the past been

able to

> optimize this For..Select query to improve speed but this time I'm

wondering

> if it's just the # of records I am trying to insert which is taking

so long.

> There are no other stored procedures or triggers involved in this

procedure

> andI insert roughly 15000 records and its taking about 1.5

minutes. Is

> there someway or technique I could use to improve this speed? Tia

Todd.

>
>
> [Non-text portions of this message have been removed]