>Ian,
>
>We have only TABLEUPDATE command within transaction. We need to do tableupdate of a dozen tables for ~1000 records to insert in each of them. These tables are involved in the relationships and have triggers and table rules. So, there are things happenning during tableupdate. But even if we turn off the table rule and triggers, the tableupdate still takes 30 seconds at least for each of the table. So, the whole saving process may take up to 10 minutes...

My Apologies Naomi. One of your earlier posts where you described what you were doing stated that you were doing some processing after the TableUpdate. I now see that you were referring to the Triggers and RI code rather than your own processing.

The only other thing I can think of processing wise would be if you could do the import in smaller chunks, retrying any that fail to make sure that they all go through in the end. Not knowing exactly what you are doing I can't tell if you can chop it into smaller steps without causing any problems. The other advantage you'll get cutting it up is if there is an update conflict you don't need to worry about reverting bits, you can revert the whole thing without loosing a huge amount of time.

If you can't shorten the duration of the transaction significantly then your only choice will be to use a TableValidate setting that will bypass the check.

Ian Simcock.