>> Ed, this is _very_ hard for FB if updated columns are indexed. Even
>>without indexes on updated columns it is hard for FB. Try to convert
>>logic of main loop to transfer it partly on client side to make
>>possible update 1000-10000 rows in one SP call and commit transaction
>>from client. FB have no and IMO never will have abilities to start and
>>commit transactions within SP.
>>
>>Best regards,
>>Alexander.

I was hoping to not have to transfer it client side though. I have
rewritten the procedure to do it in batches of 10,000. If it cannot find
any to update it will throw an exception. So I have the client continually
calling the SP and committing till it hits the exception.

Just out of curiosity, if not FB, what DB can handle tens of millions of
records with millions of updates per transaction? Or is it just a matter of
resources available to FB, like 16 GIGS of memory and faster processors.