Re^2: Fork a new process for inserting a record in DB (Oracle)

I'd look into what these two guys said above...
To avoid changing your code too much, just do all your data preparation as you currently do, but rather than executing the resutling INSERT SQL through the handle, append it to a file(s) or print it to STDOUT (and redirect it to a file) then push the resulting SQL files to your DB's buck loader.

Hope that gives you some ideas...

Comment on Re^2: Fork a new process for inserting a record in DB (Oracle)

Replies are listed 'Best First'.
Re^3: Fork a new process for inserting a record in DB (Oracle) by marto (Cardinal) on Nov 07, 2013 at 16:52 UTC
"then push the resulting SQL files to your DB's buck loader." A minor point, bulk loaders don't take sql files as input. They load text formatted files, for example CSV.	[reply]
Re^4: Fork a new process for inserting a record in DB (Oracle) by monx (Novice) on Nov 08, 2013 at 18:34 UTC
Thanks for pointing that symantic out, I agree, however there are loaders I've used in Sybase that process SQL files and they are optimized by the DB's manufacturer to handle "large loads"	[reply]
Re^3: Fork a new process for inserting a record in DB (Oracle) by Anonymous Monk on Nov 08, 2013 at 00:41 UTC
Thanx monx... This will definitely help me to tackle my situation.	[reply]