Updating mysql table
14-Nov-2020 09:07
We found this much faster than doing the indexes one by one.We will now try out if we can submit multiple such jobs in parallel (one for each partition of the table).regardsramakrishna Hi Tom, Thanks so much for your web site and help.This was a totally new paradigm for the application, and one that saved the entire mission-critical application.The in-place updates would not have worked with the terrabytes of data that we have in our database.March 17, 2003 - am UTC sorry -- I though it obvious that in most cases "no" is the answer.
With nologging, if the system aborts, you simply re-run the 'update' again, as you have the original data in the main table.The only one difference between your code and mine is that I issue just one commit at the end. Here is the numbers I've got: rebuilding indexes sequentually consistently took 76 sec., while using dbms_job.submit() calls took around 40 - 42 sec.