Give us a (literal) break

[jlcox]

I'm currently running a Compare Table Data job between two database instances and am updating from within PL/SQL Developer. This process is consuming nearly 100% of my CPU and rarely seems to want to yield for other processes. Would it be possible to thrown some Application.ProcessMessages() type statements into tight loops like these (if they currently don't exist) to allow foreground processes to get a bigger slice of the CPU pie?

 

[Marco Kalter]

I think it already runs in a background thread. Are you using a local database on the same PC where PL/SQL Developer is running? The compare function itself should never consume 100% CPU.

 

[jlcox]

No, neither database is local. The CPU consumption hits 100% during the time that the database records themselves are being inserted/updated/deleted, and seems to be much worse if done "in-place", i.e., executed directly from the compare table data results window rather than saving the file and loading it into the target system.