>
> >I did a commit after each 50 inserts.
>
> That's too frequent. Next time you run it, think in terms of

batches of

> around 8 to 10,000 per commit - that COMMIT statements, not COMMIT

RETAINING.

I always do COMMIT.
I try this next with a greater interval.
But the propebly never will be a next time

>
> It would be worth gstat-ting the indexes on that table.

I'll try this tonight when I'm all alone on the system.

If the large

> insert affected the geometry of the indexes in a signficantly

unhelpful

> way, that could account for slow searches for the next users.

This is not the case.
The system seems to run at normal speed.
The problem is, that there is no free memory on the server, and that
FBServer.Exe has used some 700 in Nonpaged Buffer !

>
> If you're alone on the system for doing large batches of inserts,

try

> deactivating indexes for the duration of the task and reactivating

them

> afterwards. It will make the batch faster; and reactivating them
> afterwards will rebuild them. After that, run SET STATS from isql,

and log

In short. Deactive index, do what ever insert I need, reactivate
and "reindex (SET STATS).

A backup - restore tonight will do the same, right ?

Michael