How to use the sql engine on a insert select of 100 milions of records? Without blowing away the undo table space? Im offen using cursor with bulk and limit. Then, forall for the dml (insert or update). But is slow very slow!
Just on the last point of the video, no one is going to praise you for making that 8 hour overnight batch job run in 30 minutes, generally I always found that such work was more about me wanting to free up db resources so that it could cope with the additional functionality being crammed into the existing system.
Very interesting and a good example of refactoring existing code.
Glad you liked it
commit frequency was a good one!
is most cases, the optimal number of commits is 1
Useful and informative, Thank you so much for your efforts, as usual you are always there with very good and simple examples.
My pleasure!
Great video!
Glad you enjoyed it
How to use the sql engine on a insert select of 100 milions of records? Without blowing away the undo table space?
Im offen using cursor with bulk and limit. Then, forall for the dml (insert or update).
But is slow very slow!
For 100s of millions, I'm probably looking at insert-append (a lot depends on whether you can handle the implications of that)
Thanks for the Great video! Is there the example code available somewhere?
Look for "oh_bulkmig" in my github rep under "office hours" github.com/connormcd
Thank you
You're welcome
Thank you.
You're welcome!
... and I still want to have or buy this OMG shirt somewhere ... 🙂
Greetings from Hessen/Good Old Germany.
Greetings from Perth but on my way to Germany (DOAG)
To hint or not to hint?
last resort
I liked the video, but "calling the web service" from the PLSQL block sounds like... the main part that should be fixed here :-D
PL/SQL was just the simple example - the same principle applies anywhere. But fair point :-)
Just on the last point of the video, no one is going to praise you for making that 8 hour overnight batch job run in 30 minutes, generally I always found that such work was more about me wanting to free up db resources so that it could cope with the additional functionality being crammed into the existing system.
Cloud changes that equation I think ... because you are literally saving real money