I read that CONSISTENCY imposes table locking even for read operations
which means that I will continue using CONCURRENCY mode. Additionally, I
will not run both update processes at the same time to avoid the problem I
have been having.
On Sat, Dec 19, 2015 at 11:01 PM, Caroline Beltran <
carolin
Alan, I think you are right. I backed up then restored my database. Next
I installed SuperServer and everything was going very well. Here are my
stats:
Database header page information:
Flags 0
Checksum12345
Generation 22516
I can reproduce this 'stalling' behavior. At the moment, the application is
importing records without delay. CPU consumption remains very low.
To stall FB, I will now run a query that will scan several thousands of records
that have just been INSERTed and UPDATEd. Before I run this query, her