Hi All!

I have strange problem.
My application inserts a lot of records in database as follow:

1. Start wait consistency transaction
2. Disable constraints and indexes on table
3. execute delete from table
4. execute select (*) from table
5. commit that transaction

It should effectively clear table and collect garbage.

Next it:
1. start new nowait read_commited rec_version transaction
2. begin insert records using SP which is actually plain insert
statement.
3. every 1000 records issue commit. I also commit all statements,
event which produced error. It should handle OIT and OAT properly I
guess.

Performanse is low. Here is the problem, I guess. When I open server
manager it shows growing "number of attachments". But, that is
strange, because I'm using only one connection in one thread.
Everything is going serialized.
After some time, when inserts continued, number of attachments goes
down to expected level.

I'm using IBX 5.04, FB 1.0. on Win2000

Any explanation will be apperciated.

I also will be glad if somebody will answer additional questions like:

1. What happens if sp is prepared in one transaction and executed in
enother one? Is it lost context or someting like that? Could it
impact performance?
2. How DB page could impact inserts? I'm using 8K now which is
bigger then Win2000 disc page.
3. What is appropriate transaction attributes for such inserts. Data
is only inserted. I tryed to set no_auto_undo option. No changes in
performance.

Mike